You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some webpack loaders have configuration which can't be expressed as a string, so can't use the current loaders means of setting config, e.g. postcss-loader and stylus-loader
The text was updated successfully, but these errors were encountered:
insin
changed the title
Support non-query config for loaders
Provide a way to add top-level config to the webpack object
Dec 10, 2015
Adding a way to either add extra things to the top level webpack config or to receive the generated config for final tweaking yourself is the nuclear option - it's so powerful that I don't want to add it until absolutely necessary.
For this one, I'm thinking that loaders in nwb.config.js should be able to define a config object which gets added to the top-level webpack config object with a pre-configured prop per loader (which loader plugin modules can configure for non-built ins which support this).
e.g. hypothetical customisation of a loader provuded by an nwb-stylus plugin:
insin
changed the title
Provide a way to add top-level config to the webpack object
Provide a way to add top-level webpack config for loaders
Dec 11, 2015
Some webpack loaders have configuration which can't be expressed as a string, so can't use the current
loaders
means of setting config, e.g. postcss-loader and stylus-loaderThe text was updated successfully, but these errors were encountered: