open-index/open-npm huggingface dataset:
npm package: @nicholaskuchiniski/mobx-debugger
Description: Mobx debugger for React Native
Latest version: 0.0.5

# React Native Logs

See your logs from React Native on Flipper.

# Usage

First you need to install the *react-native* library with `yarn mobx-debugger` or `npm i mobx-debugger`, after that you just need to configure the logger before using it:

```tsx
import { configureLogger } from "mobx-debugger";

configureLogger({
  isEnabled: __DEV__
});
```

After configuring the logger, you can use it by creating a new instance of *Logger* anywhere in your app:

```tsx
import { Logger } from "mobx-debugger";
import { interval } from  "rxjs";

const pair = new Logger("pair");
const odd = new Logger("odd");

interval(1_000).subscribe(number => {
    number % 2 === 0
      ? pair.info('Number is pair', { number })
      : odd.warn('Number is odd', { number });
});
```

And you will be able to see the logs appearing once you have *Flipper* open (Go to [Releases](https://github.com/NicholasKuchiniski/mobx-debugger/releases) to download the plugin):

![Example](./images/example.png "Example")
npm package: @nicholaskuchiniski/rn-logs
Description: React Native Logs
Latest version: 1.0.2

# React Native Logs

See your logs from React Native on Flipper.

# Usage

First you need to install the *react-native* library with `yarn rn-logs` or `npm i rn-logs`, after that you just need to configure the logger before using it:

```tsx
import { configureLogger } from "rn-logs";

configureLogger({
  isEnabled: __DEV__
});
```

After configuring the logger, you can use it by creating a new instance of *Logger* anywhere in your app:

```tsx
import { Logger } from "rn-logs";
import { interval } from  "rxjs";

const pair = new Logger("pair");
const odd = new Logger("odd");

interval(1_000).subscribe(number => {
    number % 2 === 0
      ? pair.info('Number is pair', { number })
      : odd.warn('Number is odd', { number });
});
```

And you will be able to see the logs appearing once you have *Flipper* open (Go to [Releases](https://github.com/NicholasKuchiniski/rn-logs/releases) to download the plugin):

![Example](./images/example.png "Example")
npm package: @nicholaskuchiniski/serverless-dotenv-plugin
Description: Serverless plugin template
Latest version: 2.0.1

# @nicholaskuchiniski/serverless-dotenv-plugin
Create .env files on your serverless function using serverless.yaml definition

[![npm version](https://badge.fury.io/js/%40nicholaskuchiniski%2Fserverless-dotenv-plugin.svg)](https://badge.fury.io/js/%40nicholaskuchiniski%2Fserverless-dotenv-plugin)
[![Run tests](https://github.com/NicholasKuchiniski/serverless-dotenv-plugin/actions/workflows/run-tests.yaml/badge.svg)](https://github.com/NicholasKuchiniski/serverless-dotenv-plugin/actions/workflows/run-tests.yaml)

## Why ?
The main objective of this library is to get out of the [lambda limit 4KBs problem](https://aws.amazon.com/premiumsupport/knowledge-center/lambda-environment-variable-size/#:~:text=The%20default%20quota%20value%20of,use%20an%20external%20data%20store.), using the serverless.yaml definitions to assemble the .env file (allowing to get variables through SSM, etc.). Keep in mind that putting a .env in your lambda, also means putting all your environment variables in a readable way inside your lambda .zip, so be careful.

## Usage

- Install the plugin with `yarn add -D @nicholaskuchiniski/serverless-dotenv-plugin`
- Add the plugin on you serverless.yaml:

  ```yaml
  plugins:
    - "@nicholaskuchiniski/serverless-dotenv-plugin"
  ```

- Create a custom definition on your serverless.yaml:
  ```yaml
  custom: 
    dotenv: 
      API_URL: http://api-url.example.com
  ```
- Run `serverless dotenv`, a .env file will be created on the root your actual directory and serverless will put it inside your lambda (is important to have dotenv propertly configured inside your code)

## Example
Inside the main repository, a /example exists with a simple serverless function that shows a value from the .env file.
npm package: @nicholasmole/carousel-container-component
Description: React Carousel Container Component
Author: Nicholas Mole
Latest version: 0.1.3

# Carousel Container Component

React Carousel Container Component

## Usage

Simply install the application
```
npm i @nicholasmole/carousel-container-component

```

Then add the wrapper to your Component

```
import {
	CarouselContainerComponent
} from '@nicholasmole/carousel-container-component';

<CarouselContainerComponent>
	<div>
		Slide 1
	</div>
	<div>
		Slide 2
		<div>
			Content in slide 2!
		</div>
	</div>
</CarouselContainerComponent>
```

Add divs or Component inside of the CarouselContainerComponent and each first child level Component will create a new slide.
npm package: @nicholasmole/check-size-change
Description: Check if the Window Size has change
Author: Nicholas Mole
Latest version: 0.1.1

# Check Size Change

React Parent Wrapper Component that checks if the Screen Size has change

## Usage

Simply install the application
```
npm i @nicholasmole/checkSizeChange

```

Then add the wrapper to your Component

```
export default checkSizeChange(Home);
```

Now the Home Component will have a two new booleans isMobileLimit & isTabletLimit

## Editing Default Sizes

Both of the default size checks follow bootstrap sizes

isMobileLimit: 576
isTabletLimit: 992

If you want to edit this sizes you can by sending and object to checkSizeChange using the key
words `mobile` and `tablet`


```
export default checkSizeChange(Home, {mobile: 500, tablet: 769});
```

#### Adding Custom Sizes

But what if you want to check against other sizes?

If you want to make something like `isTooSmallForMenu` with the
size of `632`

Do this: 

```
const extraSizes = [
	{
		prop: 'isTooSmallForMenu',
		limit: 632
	}
];

export default checkSizeChange(Home, {extraSizes});

```

Now the Home Component will get a new boolean prop called `isTooSmallForMenu`!

**extraSizes** can be an infinitly long array of objects

`prop:` is the name of the passed prop
`limit:` is the limit size of the prop
npm package: @nicholasmole/find-object-in-array
Description: Find an Object in an array of Objects using property and key
Author: Nicholas Mole
Latest version: 0.1.0

Find Object In Array
=========

Find an Object in an array of Objects using property and key

## Usage

`var findOinA = require('@nicholasmole/find-object-in-array');`
                                                            
```                                                                     
  var _array = [
	  {key: 'apple', color: 'red'},
		{key: 'banana', color: 'yellow'},
	];

  var result = findOinA(_array, 'key', 'apple');

// returns {key: 'apple', color: 'red'}
                               
```                                                                     

## Tests

  `npm test`

## Contributing

In lieu of a formal style guide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code.
npm package: @nicholasmole/wait-to-call
Description: Fire off function after set time
Author: Nicholas Mole
Latest version: 0.1.0

Wait To Call
=========

Fire off function after set time

## Usage

`npm i @nicholasmole/wait-to-call`
                                                                
To use WaitToCall you need to give it a function 
                                                                        
```
import {WaitToCall} from '@nicholasmole/wait-to-call';

const veryComplexAddFunction = x => console.log(x+1);

const functionToBeAttachedToButton = value => WaitToCall(veryComplexAddFunction, 500, value);                     
functionToBeAttachedToButton(5);

// output: 6
                                                                       
```

WaitToCall takes in 3 parameters

WaitToCall(executableFunction, timeBeforeFunctionCalls = 0, argumentValues)

```
 * {function} executableFunction - Function that will be called
 * {number} timeBeforeFunctionCalls - Time before function is called
 * {any}  argumentValues - Argument for executableFunction
```

## Tests

  `npm test`

## Contributing

In lieu of a formal style guide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code.
npm package: @nicholaswmin/console-plot
Description: a CLI plotter
Author: @nicholaswmin
Latest version: 0.1.21

[![test-workflow][test-badge]][test-workflow]

# console.plot 

ASCII-terminal plotter 

> wraps [asciichart][asciichart]

## Install 

```bash 
npm i --save @nicholaswmin/console-plot
```

## Usage 

```js
import console from '@nicholaswmin/console'

const arrays = {
  foo: [1,2,4,4,5,5,4,3,6,7,8,12,16,14,14,13,13,12,10,12,13,13,13,14,14,14,15],
  bar: [1,3,5,5,7,12,12,12,12,10,8,12,10,10,9,10,9,10,12,12,12,12,12,15,12,12]
}

console.plot(arrays, {
  title: 'data timeline',
  subtitle: 'Location: Okinawa, Japan',
  height: 15,
  width: 120
})
```

logs:

```js

data timeline

-- foo  -- bar

240.00 ┤                                                                                   ╭─────────────── 
233.50 ┤                                                                                 ╭─╯                
227.00 ┤                                                                               ╭─╯                  
220.50 ┤                                                                            ╭──╯                    
214.00 ┤                                                                          ╭─╯                       
207.50 ┤                                                                        ╭─╯                         
201.00 ┤                                                                      ╭─╯                           
194.50 ┤                                                                   ╭──╯                             
188.00 ┤                                   ╭──╮                          ╭─╯                                
181.50 ┤                                ╭──╯  ╰──╮                     ╭─╯                                  
175.00 ┼────╮                        ╭──╯        ╰──╮                ╭─╯                                    
168.50 ┼────╰─────╮────────────────╭─╯──────────────╰──╮─────────────╯                                      
162.00 ┤          ╰─╮           ╭──╯                   ╰─────────────────────────────────────────╮          
155.50 ┤            ╰───╮   ╭───╯                                                                ╰──╮       
149.00 ┤                ╰───╯                                                                       ╰─╮     
142.50 ┤                                                                                              ╰──╮  
136.00 ┤                                                                                                 ╰─ 

- Location: Okinawa, Japan
- last: 100 items
```

## Test 

```bash 
npm test 
```

## Authors

[@nicholaswmin][nicholaswmin]

## License

[MIT-0 License][license]

[test-badge]: https://github.com/nicholaswmin/console-plot/actions/workflows/test.yml/badge.svg
[test-workflow]: https://github.com/nicholaswmin/console-plot/actions/workflows/test.yml

[asciichart]: https://github.com/kroitor/asciichart
[nicholaswmin]: https://github.com/nicholaswmin
[license]: ./LICENSE
npm package: @nicholuassommer/pixelarticons-react
Description: DEPRECATED: This package has been renamed to @nsmr/pixelart-react
Author: Gerrit Halfmann
Latest version: 2.0.0

# DEPRECATED

This package has been renamed to [`@nsmr/pixelart-react`](https://www.npmjs.com/package/@nsmr/pixelart-react).

## Migration

Update your package.json:

```diff
- "@nicholuassommer/pixelarticons-react": "^1.0.1"
+ "@nsmr/pixelart-react": "^2.0.0"
```

Update your imports:

```diff
- import { PixelArtIcon } from '@nicholuassommer/pixelarticons-react'
+ import { PixelArtIcon } from '@nsmr/pixelart-react'
```

## Why the change?

The new package name is shorter, more concise, and easier to remember. It also better reflects the focus on pixel art icons for React.