open-index/open-npm huggingface dataset:
npm package: @movable/broccoli-rollup
Description: Rollup integration with broccoli
Author: Chad Hietala
Latest version: 2.3.0

Note: this is a (hopefully temporary) fork of the `broccoli-rollup` module.

# Usage [![Build Status](https://travis-ci.org/chadhietala/broccoli-rollup.svg?branch=master)](https://travis-ci.org/chadhietala/broccoli-rollup)

Broccoli-rollup is a simple wrapper around [Rollup](https://github.com/rollup/rollup). In the options object pass the [rollup options](https://rollupjs.org/guide/en#big-list-of-options).

#### basic

```js
var Rollup = require('broccoli-rollup');
var lib = 'lib';

module.exports = new Rollup(lib, {
  // nodeModulesPath: string Defaults to process.cwd()
  rollup: {
    input: 'lib/index.js',
    output: {
      file: 'my-lib.js',
      format: 'es',
    },
    // cache: true|false Defaults to true
  }
})
```

#### \w targets

```js
var Rollup = require('broccoli-rollup');
var lib = 'lib';

module.exports = new Rollup(lib, {
  rollup: {
    input: 'lib/index.js',
    output: [
      {
        file: 'my-lib.amd.js'
        format: 'amd',
      },
      {
        file: 'my-lib.iife.js'
        format: 'iife',
      }
    ]
  }
})
```
npm package: @movable/cordova-sdk
Description: MovableInk Cordova SDK
Author: MovableInk
Latest version: 2.2.0

# MovableInk Cordova SDK

This is a Cordova bridge for the MovableInk iOS and Android SDKs

## Installation

```sh
npm install @movable/cordova-sdk
```

Read more at
[MovableInk Documentation](https://sdk-mobile.movableink.com/sdk_wrappers/Cordova/)
npm package: @movable/data-sources-parser
Description: This library contains a library for parsing Data Sources responses in a consistent way.
Latest version: 0.5.0

# Movable Ink: Data Sources Parser

This library contains a library for parsing Data Sources responses in a consistent way.

## HTMLNormalizer

This class takes an HTML string and the URL of the HTML in its constructor. For example:

```js
import { HTMLNormalizer } from 'data-sources-parser';

new HTMLNormalizer(`
  <html>
   <body>
    <h1>Hello, world!</h1>
   </body>
  </html>
`, 'https://www.movableink.com');
```

### normalizer.document

This provides the created [document](https://developer.mozilla.org/en-US/docs/Web/API/Document) object.

```js
import { HTMLNormalizer } from 'data-sources-parser';
const { document } = new HTMLNormalizer('<html>...</html>', 'https://www.movableink.com');

const header = document.querySelector('h1');
```

### normalizer.baseURL

This provides the base URL of the page, taking into account any `<base>` tag and the provided URL:

```js
import { HTMLNormalizer } from 'data-sources-parser';
const { baseURL } = new HTMLNormalizer('<base href="/home/" />', 'https://www.movableink.com');

console.log(baseURL); // https://www.movableink.com/home/
```

### normalizers.absolutizePath

This takes a path (likely from an `href` or `src`) and converts it into its fully qualified URL, taking into account the URL and `<base>` tags of the page.

```js
import { HTMLNormalizer } from 'data-sources-parser';
const normalizer = new HTMLNormalizer('<base href="/home/" />', 'https://www.movableink.com');

const logoURL = normalizer.absolutizePath('images/logo.png');
console.log(logoURL); // https://www.movableink.com/home/images/logo.png
```

## Releases

To release a change, run the release command.

(This uses [release-it](https://github.com/webpro/release-it) for managing the releases).

```sh
yarn run release
```

By default, this will be a patch release. If you wish to release a different change:

```sh
yarn run release patch;
yarn run release minor;
yarn run release major;
yarn run release 2.8.3;
```
npm package: @movable/ember-cli-deploy-gitlab-scm-data-generator
Description: Generate SCM data for `ember-cli-deploy` on GitLab
Author: Alex LaFroscia
Latest version: 1.0.0

# `ember-cli-deploy` SCM Data Generator for GitLab

This is a tiny utility that provides an alternate [`ember-cli-deploy-revision-data` SCM data generator](https://github.com/ember-cli-deploy/ember-cli-deploy-revision-data#scm-data-generators) that is fit to use in the GitLab CI environment. It is necessary due to an issue in `git-repo-info` where it does not work correctly inside a Docker container (see [rwjblue/git-repo-info#46](https://github.com/rwjblue/git-repo-info/issues/46)).

## Usage

Install the package with

```bash
yarn add -D @movable/ember-cli-deploy-gitlab-scm-data-generator
```

Then configure `ember-cli-deploy-revision-data` to use it:

```javascript
// config/deploy.js

...
ENV["revision-data"] = {
  scm: function(context) {
    return require('@movable/ember-cli-deploy-gitlab-scm-data-generator');
  }
}
...
```
npm package: @movable/ember-cli-mirage
Description: A client-side HTTP server to develop, test and demo your Ember app
Author: Sam Selikoff
Latest version: 0.2.9-custom.6

# What is this thing??

We are currently stuck on `@movable/ember-cli-mirage@0.2.9`. This is a custom fork of it, modified to fit better into a modern Ember build process.

***

[![Build Status](https://github.com/movableink/ember-cli-mirage/workflows/Lint%20and%20Test/badge.svg)](https://github.com/movableink/ember-cli-mirage/actions?workflow=Lint+and+Test)
[![npm version](https://badge.fury.io/js/%40movable%2Fember-cli-mirage.svg)](https://badge.fury.io/js/%40movable%2Fember-cli-mirage)

# Ember CLI Mirage


A client-side server to develop, test and prototype your Ember CLI app.

<http://www.@movable/ember-cli-mirage.com/>

----

Are you tired of

- Writing one set of fixtures for your tests, and another for development?
- Wiring up tests for each of your apps manually, from scratch?
- Changing lots of files/tests when your API changes?

Ember CLI Mirage may be for you! It lets you create a client-side server using [Pretender](https://github.com/trek/pretender) to help you develop and test your app. By default, it only runs if you're not in production and if you're not proxying to an explicit API server via `ember serve --proxy`.

## Installation

```sh
ember install @movable/ember-cli-mirage  # install:addon for Ember CLI < 0.2.3
```

## Updating

This project is new and the API is subject to change. When updating your project to a newer version of Ember CLI Mirage, please consult [the changelog](/CHANGELOG.md) for any update notes.

## Getting started

Check out the [Docs](http://www.@movable/ember-cli-mirage.com/docs/v0.2.x/)!

## Support

Having trouble? Open an issue!

You can use the [Mirage Boilerplate Twiddle](https://ember-twiddle.com/eedfd390d8394d54d5bfd0ed988a5d0f) to reproduce your issue.

## Contributing

Have a look at our [Contributing guidelines](./CONTRIBUTING.md).
npm package: @movable/eslint-config
Description: Shared ESLint configuration for Movable Ink
Author: Alex LaFroscia
Latest version: 3.0.0

# `@movable/eslint-config`

## Installation

The easiest way to set up this configuration is to leverage the Yeoman generator by running the following in the root of your project:

```bash
yarn create @movable/lint-config
```

This will ask you some questions about your project and set up the configuration for you based on the answers.

---

If you want to configure your project manually, you can do the following:

Add this package, as well as ESLint and Prettier, to your `devDependencies` by running:

```bash
yarn add -D @movable/eslint-config
```

## Configuration

A few ESLint configurations are provided, based on the kind of environment you are working in.

- [Base (`@movable/eslint-config`)](./index.js')
- [Node (`@movable/eslint-config-node`)](../node/index.js')
- [Ember (`@movable/eslint-config-ember`)](../ember/index.js')
- [React (`@movable/eslint-config-react`)](../react/index.js')

This sets up some shared rules, as well as configuring ESLint to run Prettier (so that both projects do not have to be run independently). You can extend from the base configuration like so:

```json
{
  "extends": "@movable/eslint-config"
}
```

Environment-specific packages can be included as well to better suit different use-cases. Note that each one is its own Node dependency and must be installed individually.

```json
{
  "extends": ["@movable/eslint-config", "@movable/eslint-config-node"]
}
```

## Linting Your Project

It is recommended that you add the following `package.json` to create an easy way to run ESLint from the command line:

```diff
{
  "scripts": {
+   "lint": "eslint ."
  }
}
```

This allows you to run the following:

```bash
yarn lint # Report errors in your project
yarn lint --fix # Fix anything that can be fixed automatically, and report everything else
```
npm package: @movable/eslint-config-ember
Description: Shared ESLint configuration for Ember projects at Movable Ink
Author: Alex LaFroscia
Latest version: 1.0.1

# `@movable/eslint-config-ember`

## Installation

The easiest way to set up this configuration is to leverage the Yeoman generator by running the following in the root of your project:

```bash
yarn create @movable/lint-config
```

This will ask you some questions about your project and set up the configuration for you based on the answers.

---

See the `README` for the [base configuration](../base/README.md) for more details.
npm package: @movable/eslint-config-node
Description: Shared ESLint configuration for Node projects at Movable Ink
Author: Alex LaFroscia
Latest version: 1.0.0

# `@movable/eslint-config-node`

## Installation

The easiest way to set up this configuration is to leverage the Yeoman generator by running the following in the root of your project:

```bash
yarn create @movable/lint-config
```

This will ask you some questions about your project and set up the configuration for you based on the answers.

---

See the `README` for the [base configuration](../base/README.md) for more details.
npm package: @movable/eslint-config-react
Description: Shared ESLint configuration for React projects at Movable Ink
Author: Alex LaFroscia
Latest version: 1.0.1

# `@movable/eslint-config-react`

## Installation

The easiest way to set up this configuration is to leverage the Yeoman generator by running the following in the root of your project:

```bash
yarn create @movable/lint-config
```

This will ask you some questions about your project and set up the configuration for you based on the answers.

---

See the `README` for the [base configuration](../base/README.md) for more details.
npm package: @movable/eslint-config-typescript
Description: Shared ESLint configuration for TypeScript projects at Movable Ink
Author: Alex LaFroscia
Latest version: 1.0.1

# `@movable/eslint-config-typescript`

## Installation

The easiest way to set up this configuration is to leverage the Yeoman generator by running the following in the root of your project:

```bash
yarn create @movable/lint-config
```

This will ask you some questions about your project and set up the configuration for you based on the answers.

---

See the `README` for the [base configuration](../base/README.md) for more details.
npm package: @movable/generator-lint-config
Description: Yeoman generator to set up the Movable Ink linter config
Author: Alex LaFroscia
Latest version: 1.0.1

# `@movable/lint-config`

This [Yeoman](https://yeoman.io) generator automates the process of configuring different linter configurations witihn your project.

## Usage

You can run the generator through `npx` by running the following:

```bash
npx -p yo -p @movable/generator-lint-config -- yo @movable/lint-config
```

You will be asked a few questions about your project, and once answered, the any dependencies and required configuration will be taken care of for you.