open-index/open-npm huggingface dataset:
npm package: @icosahunter/condensate
Description: A responsive css library with intuitive h-box/v-box layouting, scriptless components (including sidebar!), and simple but extensive themeing through css variables.
Author: Nathaniel Markham
Latest version: 1.0.1-beta

<div align="center">
    <img src="icon.svg" width="150">
    <h1> Condensate </h1>
</div>

Condensate is a responsive css library with intuitive h-box/v-box layouting, scriptless components (including sidebar!), and simple but extensive themeing through css variables.

You can use condensate by putting the below into the `head` of your html:

`<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@icosahunter/condensate@1.0.1-beta/dist/condensate.min.css">`

If you want to add the css file to your project directly see [releases](https://github.com/Icosahunter/condensate/releases)

## Beta Release! 🎉

Condensate is now [released in beta](https://github.com/Icosahunter/condensate/releases)! I believe it is feature complete and am happy with where it is. Please give it a try and if you come across any problems create an [issue](https://github.com/Icosahunter/condensate/issues)!

## Documentation

A demo and documentation page can be found [here](https://icosahunter.github.io/condensate/).
npm package: @icose/vite-plugin-fmwv
Description: This is a Vite plugin that allows you to mock the FileMaker Web Viewer environment in your Vite project.
Author: Alexandros Raikos
Latest version: 1.1.0

# ⚡️ Vite &mdash; FileMaker Web Viewer

A Vite plugin that allows you to mock the FileMaker Web Viewer environment in your Vite project.

## Installation

```bash
npm install @icose/vite-plugin-fmwv --save-dev
```

## Usage

Add the plugin to your `vite.config.js`:

```javascript

import { defineConfig } from 'vite'

import filemakerWebViewerPlugin from '@icose/vite-plugin-fmwv'
import { 
    mockFileMakerHandlerScript,
    mockFileMakerTriggerScript
} from './src/test/scripts'

export default defineConfig({
    plugins: [
        filemakerWebViewerPlugin({
            triggerScripts: [
                {
                    label: 'mockFileMakerTriggerScript',
                    function: mockFileMakerTriggerScript
                }
            ],
            handlerScripts: [
                {
                    name: 'mockFileMakerScript',
                    function: mockFileMakerScript
                }
            ]
        })
    ]
)}
```

You can then run the `vite` command as usual, and any trigger scripts or handler scripts will be available in the preview environment. There are even buttons in the preview environment that allow you to run the mock trigger scripts.

### `triggerScripts`

This optional parameter is useful for mocking FileMaker scripts that are triggered by FileMaker and use the `Perform JavaScript in Web Viewer` script step to run JavaScript code in the Web Viewer.

An array of objects that will be available as mock scripts in the FileMaker Web Viewer environment. These functions should utilise globally available functions in the application environment (`window.someCustomFunction()`), as the actual Web Viewer does.

### `handlerScripts`

This optional parameter is useful for mocking FileMaker scripts that are receiving data from the Web Viewer using the `FileMaker.PerformScriptWithOption( script, parameter, option )`, or `FileMaker.PerformScript( script, parameter )` functions.

An array of objects that will be available as mock scripts in the FileMaker Web Viewer environment. The type of the `function` property should be:

```typescript
function mockFileMakerScript(
    script: string, // The name of the script.
    parameter?: string, // The optional string parameter passed to the script.
    option?: number // A mock option parameter
): string
```

__Note:__ The `option` parameter is optional and defaults to `0`. It is related to how connected scripts behave, check out [Options for handling the current script when starting new scripts - Claris](https://help.claris.com/en/pro-help/content/options-for-starting-scripts.html) for more information.


## Example

Check out the `tests` directory for a simple example of how to use this plugin.

## Contributing

Check out the [Contributing Guidelines](CONTRIBUTING.md) to get started on contributing to this repository.

## License

This project is licensed under the MIT License. See the [LICENSE](LICENSE.md) file for details.
npm package: @icoset/icoset-webpack-plugin
Description: Use Webpack + Icoset to build svg's dynamically into your outputed bundle.
Author: @geoctrl
Latest version: 1.0.2

# Icoset Webpack Plugin

Use Webpack + Icoset to build svg's dynamically into your outputed bundle.

Learn more about icoset: [@icoset/icoset](https://github.com/icoset/icoset/tree/master/packages/icoset)

Check out the icoset presets: [@icoset/preset-*](https://github.com/icoset/icoset)

## What it does

Since [Icoset](https://github.com/icoset/icoset) is a build-time tool, we need a way to get
all these icons into our app during run-time.

Enter `icoset-webpack-plugin` - we can now use webpack to initiate Icoset with a custom
config, and dynamically inject it into our final bundle.

## Install

```bash
// yarn
$ yarn add @icoset/icoset @icoset/icoset-webpack-plugin
```

```bash
// npm
$ npm install -s @icoset/icoset @icoset/icoset-webpack-plugin
```

## Use

```javascript
// webpack.config.js
const IcosetWebpackPlugin = require('@icoset/icoset-webpack-plugin');
const path = require('path');

module.exports = {
  entry: './src/index.js',
  output: {...},
  plugins: [
    new IcosetWebpackPlugin({
      directory: path.resolve(__dirname, 'icons'),
    })
  ],
}
```

## Options

### `icosetOptions` object (Required)

Pass in icoset options here (like `directory` and `icons`).
Check out the [Icoset README](https://github.com/icoset/icoset/tree/master/packages/icoset) to learn more.

### `entryName` string (Optional)

Depending on the webpack configuration, you might have more then one entry file.

This option allows you to target a named entry file for injection:

```javascript
module.exports = {
  entry: {
    one: './src/one.js',
    two: './src/two.js',
  },
  plugins: [
    new IcosetWebpackPlugin({
      entryName: 'one', // the plugin will inject the icons into this entry file
      icosetOptions: {
        directory: path.resolve(__dirname, 'icons'),
      },
    })
  ],
}
```

### `injectionType` "onDocumentLoad" | "window" (optional)

Choose how you want your icons added to your app.

- `onDocumentLoad` **DEFAULT** - inject svgs directly into the `<body>` on document load.
- `window` - inject svgs into a window variable for later use (window variable name defaults to `window.__icoset`).

### `windowVariableName` string (optional)

If `injectionType === 'window'`, you can change that variable name here.

```javascript
module.exports = {
  plugins: [
    new IcosetWebpackPlugin({
      injectionType: 'window',
      windowVariableName: '__whatever_you_want__',
    })
  ],
}
// output: window.__whatever_you_want__ = "<svg>...</svg>";
```

## Special Thanks

I just want to give a big shout out to our friends behind the
[`webpack-inject-plugin`](https://github.com/adierkens/webpack-inject-plugin) project. This project
utilizes that plugin to be able to inject custom code into an entry file.
npm package: @icoset/preset-devicon
Description: ## Install
Author: @geoctrl
Latest version: 0.1.6

# Icoset devicon Preset

## Install

```bash
# yarn
$ yarn add @icoset/icoset @icoset/preset-devicon

# npm
$ npm install -S @icoset/icoset @icoset/preset-devicon
```

## Use

When building your icon set, use the `preset` option instead of
`directory`:

```javascript
const icoset = require('@icoset/icoset');

icoset({
  preset: require('@icoset/preset-devicon'),
  // any other options you want
}).then(res => console.log(res));
```
npm package: @icoset/preset-evil-icons
Description: ## Install
Author: @geoctrl
Latest version: 0.1.7

# Icoset Evil Icons Preset

## Install

```bash
# yarn
$ yarn add @icoset/icoset @icoset/preset-evil-icons

# npm
$ npm install -S @icoset/icoset @icoset/preset-evil-icons
```

## Use

When building your icon set, use the `preset` option instead of
`directory`:

```javascript
const icoset = require('@icoset/icoset');

icoset({
  preset: require('@icoset/preset-evil-icons'),
  // any other options you want
}).then(res => console.log(res));
```
npm package: @icoset/preset-feather-icons
Description: ## Install
Author: @geoctrl
Latest version: 0.1.7

# Icoset Feather Icons Preset

## Install

```bash
# yarn
$ yarn add @icoset/icoset @icoset/preset-feather-icons

# npm
$ npm install -S @icoset/icoset @icoset/preset-feather-icons
```

## Use

When building your icon set, use the `preset` option instead of
`directory`:

```javascript
const icoset = require('@icoset/icoset');

icoset({
  preset: require('@icoset/preset-feather-icons'),
  // any other options you want
}).then(res => console.log(res));
```
npm package: @icoset/preset-mdi
Description: ## Install
Author: @geoctrl
Latest version: 0.0.10

# Icoset MDI (material design icons) Preset

## Install

```bash
# yarn
$ yarn add @icoset/icoset @icoset/preset-mdi

# npm
$ npm install -S @icoset/icoset @icoset/preset-mdi
```

## Use

When building your icon set, use the `preset` option instead of
`directory`:

```javascript
const icoset = require('@icoset/icoset');

icoset({
  preset: require('@icoset/preset-mdi'),
  // any other options you want
}).then(res => console.log(res));
```
npm package: @icoset/preset-simple-icons
Description: ## Install
Author: @geoctrl
Latest version: 0.1.6

# Icoset Simple Icons Preset

## Install

```bash
# yarn
$ yarn add @icoset/icoset @icoset/preset-simple-icons

# npm
$ npm install -S @icoset/icoset @icoset/preset-simple-icons
```

## Use

When building your icon set, use the `preset` option instead of
`directory`:

```javascript
const icoset = require('@icoset/icoset');

icoset({
  preset: require('@icoset/preset-simple-icons'),
  // any other options you want
}).then(res => console.log(res));
```
npm package: @icotech/core
Description: ui library for aaicco projects based on material ui
Author: A.veysinejad
Latest version: 0.1.0-alpha

# About

This is a UI library developed using _MUI_ for OMS projects.

## install:

`npm install git+https://token:rrJt5TuGc1FaXw92sCcx@gitlab.aaiccotec.com/oms/oms-client/ico-ui.git`

## build:

`npm run build`
npm package: @icouldnotfigureoutausername/helpful-functions-package
Description: Provides helpful functions so you can don't have to worry about writting redundant code
Latest version: 1.1.2

# helpful-functions-package

![GitHub package.json version](https://img.shields.io/github/package-json/v/iyanez2314/helpful-functions-package)

## Why did I make this package?

I have only been in the industry for a year and some change but I feel like a lot of the code I have seen and a lot of the code I have written has been really repetative. My response to this was "hey i'm bored lets make my first npm package" so here I am.

## Want to use some of the functions in the browser?

Here is how you can do just that

Step 1:
if you do not have a package.json file prior to using this package please copy and paste this command in your terminal:

```javascript I'm A tab
    npm init -y
```

step 2:
Once you are done with step 1 head over to https://browserify.org/ and in the project you are going to use these helpful-functions-pack execute this command in your terminal:

```javascript I'm A tab
    npm install -g browserify
```

step 3:
Create Javascript file and name it what ever your little heart desires in this example I am naming it main.js:

```javascript I'm A tab
main.js;
```

step 4:
In the file you just made in my case main.js add these 2 lines of code

```javascript I'm A tab
const helpful = require("@icouldnotfigureoutausername/helpful-functions-package");
window.helpful = helpful;
```

step 5:
Once you have added the lines of code in your file you will now need to open your terminal and execute this command:

```javascript I'm A tab
    browserify main.js -o dist/index.js
```

remember to put the name of the file where you added the code first and where you want the output to be in this case dist/index.js will be made once this command is executed.

step 6:
You should now have a file named index.js in a dist folder if that is the route you took now in you html you need to create a script tag and link the file that was created in this example I am showing you what it looks like if you named it the same as I did:

```javascript I'm A tab
<script src="./dist/index.js"></script>
```

step 7:
Now that you have linked to the file in step 6 you can now create a new javascript file and link to it right under the the one we added in step 6:

```javascript I'm A tab
   <script src="./dist/index.js"></script>
   <script src="./index.js"></script>
```

step 8:
We can now add this line of code at the very top of the index.js file:

```javascript I'm A tab
const helpful = window.helpful;
```

step 9:
Now we can use the methods that helpful provides us by doing something like this:

```javascript I'm A tab
const helpful = window.helpful;
let getRandomNum = helpful.generateMinMaxRandomNumbers(100, 200);
console.log(getRandomNum);
```