open-index/open-npm huggingface dataset:
npm package: @magnet.me/flow-web-logger
Description: Utility to render the output of flow into an interactive webpage.
Author: Tiddo Langerak
Latest version: 0.0.7

Utility to render the output of flow into an interactive webpage.

The main goal of this utility is to make it easier to navigate through flow errors:
on larger projects minor errors can often result in hundreds of lines of errors, making
it difficult to filter this down to the root cause. The HTML render of these errors allows
for collapsing parts of the error trees, which makes it much easier to navigate them. 

## Usage:

```
flow --json | flow-web-logger [--root <root>] > error-page.html
```

If the optional parameter `--root` is set then all paths will be printed relative to the root directory.
npm package: @magnet.me/magnet-test-utils
Description: Set of test utilities for Magnet.me front-end projects
Latest version: 1.0.0

Collection of test utilities for Magnet.me frontend projects.

# Usage

`npm install magnet-test-utils --save-dev`

In your `karma.conf`:

```javascript
var testUtils = require('magnet-test-utils');

module.exports = function(config) {
	return {
		files : testUtils.files.concat([
			//your files here
		])
	};
};
```
npm package: @magnet.me/mm-experiments
Description: Set of directives to integrate A/B testing in an Angular application.
Latest version: 1.2.2

[![Magnet.me Logo](https://cdn.magnet.me/images/logo-2015-full.svg)](https://magnet.me?ref=github-mm-experiments "Discover the best companies, jobs and internships at Magnet.me")

# mm-experiments

Set of directives to integrate A/B testing in an Angular application.

Usage with Google Experiments:

```javascript
app
	.run((experiments, googleExperiments) => {
		//Configure all the things
		experiments.setVariationFactory('my-experiment', () => googleExperiments.getVariation('googleExperimentId'));
	})
```
```html
	<div mm-experiment="my-experiment">
		<h1 mm-variation="0">Stuff</h1>
		<h1 mm-variation="1">Other stuff</h1>
		<p>
			Above is showing variation {{$variation}}
		</p>
	</div>
```

# Caveats

## Some experiment providers (e.g. Google Analytics) require you to send an additional request after loading the experiment
This module only loads the experiment in the browser, but does not automatically send anything to your experiments provider. For example, Google Analytics requires that at least one hit is send to Google Analytics after loading the experiments. This module does not do that for you since this we do not know how you interact with Google Analytics (this is application specific) and therefore we cannot determine an appropriate action to take to send the hit to GA.
npm package: @magnet.me/mm-on-enter-viewport
Description: Directive to detect when an element has entered the viewport
Latest version: 1.0.9

[![Magnet.me Logo](https://cdn.magnet.me/images/logo-2015-full.svg)](https://magnet.me?ref=github-mm-on-enter-viewport "Discover the best companies, jobs and internships at Magnet.me")

# mm-on-enter-viewport

Directive to detect when an element has entered the viewport

# NPM run commands

Usage: `npm run <run-command>`

## `build-standalone`
Compiles a stand-alone bundle with all dependencies bundled. The bundle can be found in `/out/mm-on-enter-viewport.bundle.js`.


This bundle should only be used for testing and documentation, but it should not be distributed or required from other modules.


## `build`

Lints the project and Compiles the source with babel to ES5. The compiled files are placed in `/out` and are suitable to be `require()`d from other modules. Additionally all resources will be copied (see `copy-resources` below).



## `copy-resources`
Copies all non-javascript files to the `out/` folder. This keeps `require(<resosurce>)` calls in the source files working after compilation.


## `lint`
Runs `jshint` to validate the project.

## `watch`
Starts the compilation in watch mode. It will lint the project **once** on startup, successive compilations will skip the linting phase.

## `clean`
Cleans up the folder by removing the docs and out folders.

## `test`
Builds a standalone bundle and runs all tests on it.

## `jenkins-test`
Same as `test`, but with the Jenkins config (only runs PhantomJS and stores the output in a junit compatible format).

## `build-docs`
Creates all document files with `ng-docs`

## `live-docs`
Build all docs and serves them on port 8080.