open-index/open-npm huggingface dataset:
npm package: @intuicio/wasm-compiler
Description: WASM compiler (supports compilation between formats: WAT, WASM, AST)
Author: Patryk 'PsichiX' Budzynski
Latest version: 1.0.10

# WASM Compiler
### Node.js and browser WASM compiler (using Wabbit - official WebAssembly WAT-to-WASM parser)

![Travis CI](https://travis-ci.org/PsichiX/wasm-compiler.svg?branch=master)

# Install
```bash
npm install --save @intuicio/wasm-compiler
```

```bash
npm install -g @intuicio/wasm-compiler
```

# CLI Usage
```bash
wasmc -i test.wast -o test.wasm
```

```
Usage: wasmc [options]

Options:
  -i, --input    Input file path                             [string] [required]
  -o, --output   Output file path                            [string] [required]
  -s, --silent   Silent                                                [boolean]
  -p, --pretty   Pretty output                                         [boolean]
  -m, --mode     Compilation mode                          [default: "wat-wasm"]
  -t, --trace    Print error stack trace                               [boolean]
  -e, --explain  Log explained WASM output                             [boolean]
  -d, --debug    Debug symbols                                         [boolean]
  -h, --help     Show help                                             [boolean]
  -v, --version  Show version number                                   [boolean]

Copyright (c) 2018
```

# API Usage
```javascript
import { wat2wasm } from '@intuicio/wasm-compiler';

const script = `(module
  (func $add (export "add") (param $a i32) (param $b i32) (result i32)
    (i32.add (get_local $a) (get_local $b))
  )
)`;
wat2wasm('test.wast', script, { explain: true, debug: true })
  .then(bytes => console.log(bytes))
  .catch(e => console.error(e));
```

# Browser Usage
```html
<!DOCTYPE html>
<html lang="en" dir="ltr">
  <head>
    <script src="https://unpkg.com/@intuicio/wasm-compiler/bin/wasm-compiler.min.js"></script>
  </head>
  <body>
    <script>
    const script = `(module
      (func $add (export "add") (param $a i32) (param $b i32) (result i32)
        (i32.add (get_local $a) (get_local $b))
      )
    )`;
    WasmCompiler.wat2wasm('test.wast', script, { explain: true, debug: true })
      .then(bytes => console.log(bytes))
      .catch(e => console.error(e));
    </script>
  </body>
</html>
```
npm package: @intuiface/cli
Description: Intuiface CLI helps you build interface assets for Intuiface
Latest version: 2.1.0

# intuiface-cli

Intuiface CLI is a command line tool that helps you build interface assets for Intuiface.  
This CLI will generate Intuiface Descriptor (*.ifd) file and build the Interface Asset (IA) to be able to add it in an Intuiface Experience.

## Usage: 
Command to build an Interface Asset:
```sh 
npx intuiface-cli build -n IA_File_Name
```


| Option            | Description                                                                                     |
|--------------------|-------------------------------------------------------------------------------------------------|
| `-n, --name <name>` | Name of the interface asset's main file in the `src/*` folder (without extension).             |
| `-i, --icon [icon]` | Path to the icon of the IA displayed in Composer Interface Asset panel.                        |
| `-d, --debug`       | Build in debug mode.                                                                          |
| `-h, --help`        | Display help for the command.                                                                 |

To see more usage information, use the `help` command:
```
npx intuiface-cli help
npx intuiface-cli help <command>
```

### Adding an icon
If you want to add an icon to your IA, add an image in your project and reference its path in the `package.json` file editing the `build` script.

`"build": "npx intuiface-cli build -n IA_File_Name -i MyIcon.png` 

or

`"build": "npx intuiface-cli build -n IA_File_Name -i ./icons/MyIcon.png`

then run command 
```sh
npm run build
```

### Build for debug
You can run the command 
```sh
npm run build:debug
```
directly in your project. This command will not minimize the output file in order to be easier for debug. Then in the Composer Play Mode, you can use key combination `Ctrl+Shift+I`
to debug.

## Migration to v2
For existing project created before the v2 of the `intuiface-cdk`, you can migrate your project.
First, update `@intuiface/core` to use the latest version:
```
npm install @intuiface/core@latest
```
Then checks that your project still build or fix the breaking changes.

Now, you can migrate your project to use the new `intuiface-cli`. Install it with the command:
```sh
npm install @intuiface/cli
```
then use the `migrate` command to automatically upgrade your project to be compatible with CLI:
```sh
npx intuiface-cli migrate
```
npm package: @intuiface/components
Description: The components library of intuiface
Latest version: 2.1.0

<p align="center">
    <a href="https://www.intuiface.com">
        <img src="https://assets-global.website-files.com/6090f790a8effe00c12b39d0/6090f790a8effef0002b3c56_Intuiface%20logo%20animated.gif" alt="Intuiface logo" width="200" height="86">
    </a>
</p>

**@intuiface/components**

***

# @intuiface/components

## Enumerations

- [EBackgroundType](/docs/components/enumerations/EBackgroundType.md)
- [EFillDirection](/docs/components/enumerations/EFillDirection.md)
- [EFillBehavior](/docs/components/enumerations/EFillBehavior.md)
- [EPlayableState](/docs/components/enumerations/EPlayableState.md)
- [ETextHorizontalAlignment](/docs/components/enumerations/ETextHorizontalAlignment.md)

## Classes

- [CollectionComponent](/docs/components/classes/CollectionComponent.md)
- [ElementContainerComponent](/docs/components/classes/ElementContainerComponent.md)
- [ElementComponent](/docs/components/classes/ElementComponent.md)
- [BackgroundBehavior](/docs/components/classes/BackgroundBehavior.md)
- [ButtonBehavior](/docs/components/classes/ButtonBehavior.md)
- [AutoScrollBehavior](/docs/components/classes/AutoScrollBehavior.md)
- [CollectionBehavior](/docs/components/classes/CollectionBehavior.md)
- [FocusingCollectionBehavior](/docs/components/classes/FocusingCollectionBehavior.md)
- [HomogeneousBehavior](/docs/components/classes/HomogeneousBehavior.md)
- [IndexingBehavior](/docs/components/classes/IndexingBehavior.md)
- [OpeningCollectionBehavior](/docs/components/classes/OpeningCollectionBehavior.md)
- [OrientedBehavior](/docs/components/classes/OrientedBehavior.md)
- [PannableBehavior](/docs/components/classes/PannableBehavior.md)
- [ScrollableBehavior](/docs/components/classes/ScrollableBehavior.md)
- [FillBehavior](/docs/components/classes/FillBehavior.md)
- [GestureBehavior](/docs/components/classes/GestureBehavior.md)
- [TimelineBehavior](/docs/components/classes/TimelineBehavior.md)
- [VolumeBehavior](/docs/components/classes/VolumeBehavior.md)
- [PlayableMediaFacade](/docs/components/classes/PlayableMediaFacade.md)
- [PlayableBehavior](/docs/components/classes/PlayableBehavior.md)
- [SourceBehavior](/docs/components/classes/SourceBehavior.md)
- [TapBehavior](/docs/components/classes/TapBehavior.md)
- [TextInputBehavior](/docs/components/classes/TextInputBehavior.md)
- [TextBehavior](/docs/components/classes/TextBehavior.md)
- [ToggleButtonBehavior](/docs/components/classes/ToggleButtonBehavior.md)
- [TransformBehavior](/docs/components/classes/TransformBehavior.md)
- [SharingService](/docs/components/classes/SharingService.md)

## Functions

- [IntuifaceComponent](/docs/components/functions/IntuifaceComponent.md)


## Help
Found a problem, a bug? Or need some help?  
Please do not create an issue in Github! Ask us via our Support page : https://support.intuiface.com/
npm package: @intuiface/interface-asset
Description: Schematic to create an interface asset.
Latest version: 2.1.0

<p align="center">
  <a href="https://www.intuiface.com//">
    <img src="https://assets-global.website-files.com/6090f790a8effe00c12b39d0/6090f790a8effef0002b3c56_Intuiface%20logo%20animated.gif" alt="Intuiface logo" width="200" height="86">
  </a>
</p>

# Interface Asset Schematics 
This article describes how to design an interface asset, build it, and generate an IFD for use in Intuiface Composer

## Table of contents

- [Prerequisites](#prerequisites)
- [Install](#install)
- [Usage](#usage)
- [Help](#help)

## Prerequisites

- [NodeJS](https://nodejs.org/) so you can use NPM to manage your project’s dependencies
- [Visual Studio Code](https://code.visualstudio.com/) to code, build, and test your project
- [Angular Schematics CLI](https://www.npmjs.com/package/@angular-devkit/schematics-cli). Install it using NPM:  
`npm install -g @angular-devkit/schematics-cli`

## Install
Install the interface asset schematics: 
    `npm install @intuiface/interface-asset`

## Usage
First, inside a new folder, install the `interface-asset` schematics:
```
npm install @intuiface/interface-asset
```

Then initialize your interface asset workspace by using the schematics:  
```
schematics @intuiface/interface-asset:create
``` 
It will prompt you for the interface-asset name and then will create all files.

⚠️ Please use only alphanumeric characters in the name of your interface-asset (no "-", no special characters, etc). The schematics will accept it but may fail when you try to build your project.

After installation is complete, restart VSCode if you want the code analyzer running. You can use the command `npm run lint` if you want to run the code analyzer manually. We provide automatic linting (code analyzing) in VSCode through the `settings.json` file in the `.vscode` folder.

Develop your interface asset using the skeleton or read the documentation for [Intuiface Core](/docs/core/README.md)

Then run `npm run build` to build for production or `npm run build:debug` to debug your interface asset. You can use the [Command Line](/libs/cli/README.md).

## Migrate project (<2.x) to use `intuiface-cli`
Intuiface CDK v2.0.0 introduce a new command line tool [`intuiface-cli`](/libs/cli/README.md) to better handle building interface asset and generating descriptor file. You can migrate your old project to use the new CLI by following the [migration guide](/libs/cli/README.md#migration-to-v2)

## Help

Found a problem, a bug? Or need some help? 
Please do not create an issue in Github! Ask us via our Support page : https://support.intuiface.com/
npm package: @intuit/renovate-config
Description: [![npm](https://img.shields.io/npm/v/@intuit/renovate-config.svg)](https://www.npmjs.com/package/@intuit/renovate-config) [![CircleCI](https://circleci.com/gh/intuit/renovate-config/tree/master.svg?style=shield)](https://circleci.com/gh/intuit/renovate-co
Author: David Aghassi
Latest version: 1.2.5

# @intuit/renovate-config

[![npm](https://img.shields.io/npm/v/@intuit/renovate-config.svg)](https://www.npmjs.com/package/@intuit/renovate-config)
[![CircleCI](https://circleci.com/gh/intuit/renovate-config/tree/master.svg?style=shield)](https://circleci.com/gh/intuit/renovate-config/tree/master)
[![Renovate enabled](https://img.shields.io/badge/renovate-enabled-brightgreen.svg)](https://renovatebot.com/)

This repo serves as the base line for all renovate configs used within Intuit. By default, this config will attempt to auto merge all patch updates as well as dev dependencies.

## Install

```bash
yarn add @intuit/renovate-config --dev
```

And then go to your renovate config locally and add:

```json
"extends": ["@intuit"]
```

# Usage

You don't have to do anything beyond the above if you are ok with the defaults. However, if you would like to customize your usage, you can change the config in your repo to extend and change certain rules for your teams needs.

## Resources

You can learn more about configuring Renovate with [shareable configs](https://renovatebot.com/docs/config-presets/)
You can learn more about [Renovate](http://renovatebot.com)
npm package: @intuivo/intuivo_vite-plugin-svelte
Description: ## usage
Author: jesusalc
Latest version: 1.0.2

# jesusalc/vite-plugin-svelte

## usage

```js
// vite.config.js
const svelte = require('@svitejs/vite-plugin-svelte')
const { defineConfig } = require('vite')

module.exports = defineConfig(({ command, mode }) => {
  const isProduction = mode === 'production'
  return {
    plugins: [
      svelte({
        /* inline options here */
      })
    ],
    build: {
      minify: isProduction
    }
  }
})
```

## Options

vite-plugin-svelte reads the vite configuration and uses an appropriate default configuration

It also loads `svelte.config.js` (or `svelte.config.cjs`) from the configured `vite.root` directory automatically.

Options are applied in the following order:

1. vite-plugin-svelte defaults
2. svelte.config.js in vite.root
3. inline options passed in vite.config.js

It supports all options from rollup-plugin-svelte and some additional options to tailor the plugin to your needs.

For more Information check [options.ts](src/utils/options.ts)

## License

MIT
npm package: @intuned/ata
Description: A dependency for downloading `*.d.ts` files corresponding to a Node.js source file. Relies on API's provided by [jsdelivr](https://www.jsdelivr.com).
Latest version: 0.0.11

# TypeScript - Automatic Type Acquisition

A dependency for downloading `*.d.ts` files corresponding to a Node.js source file. Relies on API's provided by [jsdelivr](https://www.jsdelivr.com).

### Usage

```ts
// Create the function for running ATA with a series of callbacks
const ata = setupTypeAcquisition({
  projectName: "My ATA Project",
  typescript: ts,
  logger: console,
  delegate: {
    receivedFile: (code: string, path: string) => {
      // Add code to your runtime at the path...
    },
    started: () => {
      console.log("ATA start")
    },
    progress: (downloaded: number, total: number) => {
      console.log(`Got ${downloaded} out of ${total}`)
    },
    finished: vfs => {
      console.log("ATA done", vfs)
    },
  },
})

// Run that function with the new sourcefile
ata(`import danger from "danger"`)
```

You can call `ata` when it is convenient to you, it will not grab the same dependencies twice. The callbacks for `started` and `finished` are only triggered when some work is going to happen, so you can use those for UI elements show/hide. `progress` is triggered every 5 downloads.

### How it works

At a high level, for this input code:

```
import danger from "danger"
```

The library will

- Look for the latest npm module of "danger", then get its file list
- As there are `.d.ts` files to download in the dep, then it triggers `started`
- Download the `*.d.ts` files for "danger" from the npm module "danger"
- Read those `.d.ts` and look at these modules from usage:
  - `"node-fetch"` - it sees that "node-fetch" has no `.d.ts` files and gets them from "@types/node-fetch"
  - `"commander"` - it sees that command ships its own types
  - `"@octokit/rest"` - it sees that octokit/rest ships its own types
  - `"gitlab"` - it also sees
- Recurse though their dependencies too.
- Once those are done, trigger `finished` with a Map of the `vfs` if you prefer to set them in bulk.

### Niceties

Users can give a specific npm version or tag to work from instead of the default "latest":

```ts
import { xy } from "xyz" // types: beta
```

If this isn't something you want, I'm not against a flag to disable it.