![\"webpack-nano\"](\"https://raw.githubusercontent.com/shellscape/webpack-nano/master/assets/nano.svg?sanitize=true\")
\n
![](\"https://c5.patreon.com/external/logo/become_a_patron_button@2x.png\"){kind=logo}
\n\n\n## Requirements\n\n`webpack-nano` is an evergreen module. š² This module requires an [Active LTS](https://github.com/nodejs/Release) Node version (v10.0.0+).\n\n## Benefits\n\n- Holy bananas š it's itsy bitsy\n- Doesn't hit you over the head with an avalanche of flags and options\n- Allows any number of user-defined flags\n- It does one thing: tells webpack to start a build\n- ~90% smaller than webpack-cli and webpack-command\n\n## Usage\n\n```console\n$ npx wp --help\n\n Usage\n $ wp [...options]\n\n Options\n --config A path to a webpack config file\n --config.{name} A path to a webpack config file, and the config name to run\n --json Emit bundle information as JSON\n --help Displays this message\n --silent Instruct the CLI to produce no console output\n --version Displays webpack-nano and webpack versions\n\n Examples\n $ wp\n $ wp --help\n $ wp --config webpack.config.js\n $ wp --config.serve webpack.config.js\n```\n\n## Custom Flags\n\nWith `webpack-cli` users are limited as to the flags they can use on with the `$ webpack` binary, and are instructed to use the `--env` flag for custom data. Well that's just šš. With `webpack-nano` users can specify an unlimited number of custom flags, _without restriction_.\n\nSay you have a bundle which can be built to use different asset locations from cloud data sources, like Amazon S3 or Google Cloud Storage. And in this scenario you prefer to specify that location using a command-line flag. If you were using `webpack-cli`, you'd have to use the `--env.source` flag (or you'd get a big 'ol error) and use a function for your `webpack.config.js` export. Using `webpack-nano`:\n\n```console\n$ wp --config webpack.config.js --source s3\n```\n\n```js\n// webpack.config.js\nconst argv = require('webpack-nano/argv');\n\nconst { source } = argv;\n\nmodule.exports = {\n ...\n}\n```\n\nāØ Magic. The `webpack-nano/argv` export provides quick and easy access to parsed command-line arguments, allowing the user to define the CLI experience as they want to.\n\n## Special Configuration File Types\n\nWebpack configuration files can be written using a variety of module loaders. e.g. Babel or TypeScript. `webpack-nano` allows users to use file types like `webpack.config.babel.js`, `webpack.config.es6`, `webpack.config.mjs`, and `webpack.config.ts`. Users are responsible for installing a compatible module loader when using these special file types. The table below represents the supported file types and their compatible loaders:\n\n| Extension | Compatible Loaders |\n| ------------| ------------------ |\n| `.babel.js` | `@babel/register`, `babel-register`, `babel-core/register`, `babel/register` |\n| `.babel.ts` | `@babel/register` |\n| `.es6` | `@babel/register` |\n| `.mjs` | `@babel/register` |\n| `.ts` | `ts-node/register`, `typescript-node/register`, `typescript-register`, `typescript-require` |\n\n## Build Stats\n\nThis project attempts not to make assumptions about how a build should behave, and that includes webpack [`stats`](https://webpack.js.org/configuration/stats/). By default, `webpack-nano` will apply two `stats` options: `colors` (based on [`supports-color`](https://github.com/chalk/supports-color) and `exclude: ['node_modules']`). These can be quickly overridden by including these key/values in your stats configuration.\n\n## Meta\n\n[CONTRIBUTING](./.github/CONTRIBUTING.md)\n\n[LICENSE (Mozilla Public License)](./LICENSE)\n","readmeFilename":"README.md","homepage":"https://github.com/shellscape/webpack-nano","repository":{"type":"git","url":"git+https://github.com/shellscape/webpack-nano.git"},"bugs":{"url":"https://github.com/shellscape/webpack-nano/issues"}}