Webpack is in many regards a must have for large scale JS Application development. Through it's numerous extensions it also supports many other crucial aspects for web development. The goal of this addon is to abstract a lot of the complex configuration requred to get a solid workflow setup for large scale application development.
Note: the current version of this extension was specifically designed for creating server side rendered react applications. Though our ultimate goal is to provide a more general development platform we want to first nail this subset before conquering others.
To install this addon simply run the following with NPM
Note: This API is likely to be broken into a set of more modular APIs in future versions.
|CLI entry point for interfacing with Webpack.|
NOTICE: This API is likely to be broken into a set of more modular APIs in future versions.
|Yes||N/A||Determines how to build Webpack.|
Based on the task provided Webpack will be built in one of two modes.
|Builds Webpack for production.|
|Runs Webpack in watch mode for local development.|
|Allows bundling of external dependencies. This is automatic for client builds. Node/Server builds require this to be passed explicitly.|
|Public path an application will be mounted at. Generally the default value is recommended.|
|Sets a flag for webpack to include source mapping.|
|Enables circular dependency checking|
|Sets a flag for webpack to output "records" with profiling.|
|Output static "stats" via |
|Provides directory path for stats output. Generally the default value is recommended.|
|Tells Webpack to run in development mode. The default is "production".|
|Host development server will be running on. Generally the default value is recommended.|
|Defines a pattern for ignoring paths for file watching.|
|Sets a flag for webpack to output "records" with profiling and stats.|
|Set polling frequency. |
|Port to bind development server to.|
|Expected protocol for development server.|
|Run "stats" via |
|Host stats server will be running on. Generally the default value is recommended.|
|Sets the base port for both client and server "stats" using |
It is recommended to keep polling on for cross platform purposes. File watching can be CPU intensive if a system falls back to fs.watchFile versus utilizing file system events with fs.watch. This is common on linux environments.
To run Webpack in development/watch mode on a specific port you.
Or build with Webpack for production.
Of course you can also just use the default values which are recommended.