
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
webpack-config
Advanced tools
Helps to load, extend and merge webpack configs
npm install webpack-config --save-dev
or
yarn add webpack-config --dev
#extend()
- Helps to extend config using local file or shareable config#merge()
- Helps to merge some values into config and overrides existing ones#defaults()
- Helps to add some values if they are missingenvironment
variables under #extend()
, #merge()
, #defaults()
methodsprocess.env.*
variables in addition to environment
onesnode
-modulesDetails changes for each release are documented in the release notes and also in the wiki page.
You can publish your configs to npm
using webpack-config-
prefix for package name.
When you call #extend()
method you may omit that prefix:
import Config from 'webpack-config';
export default new Config().extend(
'mdreizin/base',
'mdreizin/css',
'mdreizin/html',
'webpack-config-mdreizin/json'
// etc
);
Also I would recommend to add webpack
and webpack-config
keywords so other users can easily find your module.
./webpack.config.js
import Config, { environment } from 'webpack-config';
environment.setAll({
env: () => process.env.NODE_ENV
});
// Also you may use `'conf/webpack.[NODE_ENV].config.js'`
export default new Config().extend('conf/webpack.[env].config.js');
./conf/webpack.base.config.js
import ExtractTextPlugin from 'extract-text-webpack-plugin';
import Config from 'webpack-config';
const extractCss = new ExtractTextPlugin('[name].css');
export default new Config().merge({
output: {
filename: '[name].js'
},
resolve: {
root: [
__dirname
],
modulesDirectories: [
'node_modules'
]
},
plugins: [
extractCss
],
module: {
loaders: [{
test: /\.less$/,
loader: extractCss.extract('style', [
'css',
'less'
])
}]
}
});
./conf/webpack.development.config.js
import webpack from 'webpack';
import Config from 'webpack-config';
export default new Config().extend('conf/webpack.base.config.js').merge({
debug: true,
devtool: '#source-map',
output: {
pathinfo: true
},
entry: {
app: [
'src/index.js',
'src/index.less'
],
vendor: [
'lodash'
]
},
plugins: [
new webpack.optimize.CommonsChunkPlugin('vendor', 'vendor.js')
]
});
./conf/webpack.production.config.js
import webpack from 'webpack';
import Config from 'webpack-config';
export default new Config().extend({
'conf/webpack.development.config.js': config => {
delete config.debug;
delete config.devtool;
delete config.output.pathinfo;
return config;
}
}).merge({
plugins: [
new webpack.optimize.DedupePlugin(),
new webpack.optimize.OccurrenceOrderPlugin(true),
new webpack.optimize.UglifyJsPlugin({
mangle: true,
output: {
comments: false
},
compress: {
warnings: false
}
})
]
});
FAQs
Helps to load, extend and merge webpack configs
The npm package webpack-config receives a total of 0 weekly downloads. As such, webpack-config popularity was classified as not popular.
We found that webpack-config demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.