open-index/open-npm huggingface dataset:
npm package: @rei/front-end-build-configs
Description: Build configs for REI apps, libraries, and components
Latest version: 1.3.0

# REI Build Config Files

This repository contains build configurations for:

* REI micro-site front-end application bundles.
* Libraries (future)
* Components (future)

## Installation

    npm install @rei/front-end-build-configs 

## Building

### Applications

If you are using [FEBS](https://github.com/rei/febs), you do not need to install as this is already
a dependency of `FEBS`.

Otherwise, build your application with `webpack --config <path to config> --env <env>`. 

### Libraries

Stay tuned!

### Components
 
Stay tuned!

## Overriding configurations

If you are using `FEBS`, see its documentation for overriding the base configs.

If you are using `webpack` directly, start with these configurations and override them locally in a separate overrides file that merges them, i.e.

```
// Local webpack.config.prod.js example

const { baseConf } = require('@rei/front-end-build-configs').profiles.application;
const merge = require('webpack-merge');

return merge(baseConf('prod'), {
    /* overrides *.
});

```

Benefits in doing this:
  - You will receive upstream updates as the base configs are updated. 
  - Will help with debugging your build.
  - Will reduce proliferation of disparate build configurations that need to be maintained.

## Submit a PR to update the base configs

If you have an override or update that you think would benefit everyone, please create PR to get this pulled into the base config!

Additionally, less and less overriding will be required in new projects.

## Future

* Library and component build configs ("Technology profiles").
npm package: @rei/gulp-html-include
Description: HTML include generator for static assets, e.g., foo.min.js => foo.min.js.html
Author: Derek Peterson
Latest version: 1.0.0

# gulp-html-include [![Build Status][travis-image]][travis-url]

> HTML include generator for static assets, e.g., foo.min.js => foo.min.js.html

## Usage

This plugin generates an HTML file with solely a `script` or `link` reference
to JS or CSS files passed to it, respectively. It pairs well with
[gulp-rev](https://github.com/sindresorhus/gulp-rev) and
[gulp-rename](https://github.com/hparra/gulp-rename) to make it easy to include
dynamically named static files (e.g., via
[JSP](http://en.wikipedia.org/wiki/JavaServer_Pages) `include`). Now you can
enjoy versioned files without having to manually update the references to your
generated files.

```js
gulp.src( '/path/to/my/files' )
    .pipe( rev() )
    .pipe( include() )
    .pipe( rename(function ( dir, base, ext ) {
        return base.replace( /\-[^\.]+/, '' ) + ext;
    }))
    .pipe( gulp.dest( '/path/to/web/root' ) )
```

You can optionally pass in the path to prefix these files with (e.g.,
`/static/`) and the destination directory to set as the base for these files
(e.g., `../../static/`). The default path prefix is `/`, and the default
destination directory is `./`.

```js
gulp.src( '/path/to/my/files' )
    .pipe( rev() )
    .pipe( include( { path: '/static/', dest: '../../static/' } ) )
    .pipe( rename(function ( dir, base, ext ) {
        return base.replace( /\-[^\.]+/, '' ) + ext;
    }))
    .pipe( gulp.dest( '../../static' ) )
```

By default this plugin does not use self-closing tags for the `link` reference. You can enable XHTML-compliant output by setting the `xhtml` option to `true`.

```js
gulp.src( '/path/to/my/files' )
    .pipe( rev() )
    .pipe( include( { xhtml: true } ) )
    .pipe( rename(function ( dir, base, ext ) {
        return base.replace( /\-[^\.]+/, '' ) + ext;
    }))
    .pipe( gulp.dest( '/path/to/web/root' ) )
```


## Testing

You can run the tests with [Mocha](http://mochajs.org/) by
running `npm run test` in the project directory.

## License

MIT © 2019 Recreational Equipment Inc.

[travis-url]: https://travis-ci.org/reidev/gulp-html-include
[travis-image]: https://travis-ci.org/reidev/gulp-html-include.svg
npm package: @rei/vunit
Description: Write unit tests against your Vue components using mocha and vue-test-utils
Author: Alex Perkins
Latest version: 4.1.1

# vunit - Vue unit testing tools

## Description

Unit testing tool for [Vue.js](https://vuejs.org/) components. This tool allows you to easily test your Vue components using [mocha](https://mochajs.org) and [@vue/test-utils](https://vue-test-utils.vuejs.org/). Additionally, it provides code-coverage reporting via [nyc/istanbul](https://istanbul.js.org/) for both Vue components and vanilla js. It is based on the following documents:
 * [vue-test-utils
for Mocha](https://vue-test-utils.vuejs.org/guides/testing-single-file-components-with-mocha-webpack.html)
 * [example](https://github.com/vuejs/vue-test-utils-mocha-webpack-example)

## Installation

    npm install --save-dev @rei/vunit @vue/test-utils

## Basic Usage

### Running Unit Tests

    npx vunit --spec=<glob-to-specs> [--watch]

### Running Test Coverage

    npx vunit --spec=<glob-to-specs> --coverage [--watch]

    Report is generated at `./coverage`

## Creating Unit Tests

* Refer to the [@vue/test-utils documentation](https://vue-test-utils.vuejs.org/) for examples and [API](https://vue-test-utils.vuejs.org/api/).
* Create your spec files via [mocha](https://mochajs.org) syntax.
* [Chai's expect](https://www.chaijs.com/api/bdd/) is made globally available in your spec files for assertions.

## Update `npm test` Script(s)

Add `test` script to your `package.json`:

    {
        ...
        "scripts": {
            "test": "vunit --spec=<glob-to-specs>"
        },
        ...
    }

## Command-line Options

The following options are available to the tool:

    spec:               {String}    The path glob to your Vue unit tests (required)
    webpack-config:     {String}    The path to your webpack.config.js (optional)
    watch:              {String}    Comma-separated list of directories to watch for changes, e.g.
    --watch=src,test (optional).
    coverage:           {None}      Flag indicating whether or not to run coverage. Report is generated at `./coverage-vue`
    require:            {None}      Path to include a module (like a setup script) before loading tests (optional)

## Overriding the NYC Code Coverage Configuration

If you need to modify any of the [NYC test coverage configuration options](https://github.com/istanbuljs/nyc#common-configuration-options)
that are provided by default, you can create a local `.nycrc` config file and configure as needed. 

Start by just copying the [default .nycrc file](./.nycrc) to your local directory and modify as needed.

## Programmatic API

To use package via programmatic API, just `require` the module and call the exposed `run` command
 with above options passed in as an object:

    const vunit = require('vunit');
    vunit.run({
        spec: '/glob/to/specs',
        ...
    });