@vanportal/van

Vanportal CLI toolkit.

Usage no npm install needed!

<script type="module">
  import vanportalVan from 'https://cdn.skypack.dev/@vanportal/van';
</script>

README

@vanportal/van

Vanportal CLI toolkit.

Usage: van <command>

Commands:
  van babel       Babel with our opinionated defaults               [aliases: b]
  van eslint      ESLint with our opinionated defaults              [aliases: e]
  van serverless  Serverless with our list of supported plugins   [aliases: sls]
  van webpack     Webpack with our opinionated defaults             [aliases: w]

Options:
  --help     Show help                                                 [boolean]
  --version  Show version number                                       [boolean]

Examples:
  van eslint .
  van babel --help
  NODE_ENV=production van webpack src -o dist.js


External tools

These useful tools are also included as peerDependencies without the van wrapping, execute directly with npx <NAME>:

node_modules/.bin
├── babel-node -> ../../../../node_modules/@babel/node/bin/babel-node.js
├── concurrently -> ../../../../node_modules/concurrently/bin/concurrently.js
├── eslint -> ../../../../node_modules/eslint/bin/eslint.js
├── jq -> ../../../../node_modules/@vanportal/van/bin/jq
├── js-yaml -> ../../../../node_modules/js-yaml/bin/js-yaml.js
├── nodemon -> ../../../../node_modules/nodemon/bin/nodemon.js
├── npm-check -> ../../../../node_modules/npm-check/bin/cli.js
├── sort-package-json -> ../../../../node_modules/sort-package-json/index.js
├── van -> ../../../../node_modules/@vanportal/van/bin/van.js
├── webpack -> ../../../../node_modules/webpack/bin/webpack.js
└── webpack-cli -> ../../../../node_modules/webpack-cli/bin/cli.js

0 directories, 11 files

Features

  1. All-in-one development dependency
  2. Execute <command> at current working directory
  3. Load our defaults if no configurations found at current working directory
  4. By default load .env and export to <command> through process.env
    1. Load .env.dev or .env.prod if NODE_ENV is set to development or production
    2. Load .env.${NODE_ENV} otherwise
    3. Variables from .env will NOT override those already set in environment