We can configure Direflow's build process and other global configurations in
The path, relative to
src, of the folder containing Direflow Components.
This folder must contain a flat list of subdirectories, each containing a Direflow Component.
The filename of the main bundle.
⚠️ This does not work using the
The filename of the vendor bundle.
When enabling this option, all source map files will be emitted along with the main bundle.
When enabling this option, the public
index.html file will be emitted along with the main bundle.
When enabling this option, all static files will be emitted.
Direflow is build upon create-react-app, so a lot of files unuasable with Direflow will be emitted.
It's recommended to keep this option set to
To split your bundle into a chunk per Direflow Component, use the
This will create a build folder containing a bundle-file per Direflow Component.
main.js file will contain the code in your main
If the main
index.js file is empty, the
main.js file can be excluded.
When you build your Direflow Components, you can use the
This will create a build folder containing two bundle-files:
direflowBundle.js: Will contain all source-code.
vendor.js: Will contain all third-party packages.
If you want to provide your own React and ReactDOM modules. Provide the url on these fields.
Allows us to take full control over the Web Components polyfills.
Value can either be
false to disable lazyloading of the polyfills, or a path to a URL from where the polyfill should be loaded.