Resolved config doesn't contain a resolve configuration
See original GitHub issueI’ve seen this issue in a closed github issue, but I just installed v2.0.0
of this plugin and received the same issue. Here are my configs for reference:
Webpack.config
const config = Object.assign({
entry: entryPoint,
output: {
filename: outputFileName,
library: libraryName,
libraryTarget: 'umd',
umdNamedDefine: true
},
module: {
loaders: [{
test: /\.(jsx|js)$/,
exclude: /(node_modules)/,
loader: 'babel',
query: {
presets: ['es2015', 'react'],
plugins: ['transform-object-rest-spread', 'transform-class-properties']
}
}, {
test: /\.(styl|css)$/,
loader: 'style-loader!css-loader!postcss-loader!stylus-loader'
}, {
test: /\.(woff2|woff|eot|ttf|svg|otf|png|jpg|jpeg)$/,
exclude: /(node_modules)/,
loader: 'url-loader'
}]
},
postcss: function () {
return [require('autoprefixer')({
browsers: [
'last 2 versions'
]
})];
},
resolve: {
alias: {
'jquery-ui': 'jquery-ui/ui/widgets',
'sharedScript': path.resolve('./shared/script')
},
extensions: ['', '.jsx', '.js', '.styl']
},
plugins: [new webpack.DefinePlugin({
'process.env': {
NODE_ENV: '"development"',
UNITY_ENV: '"production"', // If you're building a DEV build from the Unity interface, change this to "development",
BUILD_VERSION: '"' + readVersionNumber(args) + '"',
JAVASCRIPT_INTERFACE_NAME: '"' + (buildForRP ? 'ProspectorJavascriptInterface' : 'OnsightJavascriptInterface') + '"',
LIBRARY_NAME: '"' + libraryName + '"'
}
})]
}, production ? {
plugins: [new webpack.optimize.UglifyJsPlugin({
compress: {
sequences: true,
booleans: true,
warnings: false,
drop_debugger: true,
drop_console: true
},
mangle: {
except: ['$']
},
comments: false
}), new webpack.DefinePlugin({
'process.env': {
NODE_ENV: '"production"',
UNITY_ENV: '"production"', // If you're building a DEV build from the Unity interface, change this to "development",
BUILD_VERSION: '"' + readVersionNumber(args) + '"',
JAVASCRIPT_INTERFACE_NAME: '"' + (buildForRP ? 'ProspectorJavascriptInterface' : 'OnsightJavascriptInterface') + '"',
LIBRARY_NAME: '"' + libraryName + '"'
}
})]
} : {});
module.exports = config;
package.json babel config
"babel": {
"presets": [
"es2015",
"react"
],
"plugins": [
"transform-object-rest-spread",
"transform-class-properties",
["babel-plugin-webpack-alias", { "config": "./webpack.config.js", "findConfig": true }]
]
}
Error, for reference
throw err;
^
Error: D:/web/webpack.config.js: The resolved config file doesn't contain a resolve configuration
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (6 by maintainers)
Top Results From Across the Web
Field 'browser' doesn't contain a valid alias configuration
In my webpack.config.js file I was only resolving TypeScript files i.e. ... Field 'browser' doesn't contain a valid alias configuration.
Read more >Resolve | webpack
A list of directories where requests of server-relative URLs (starting with '/') are resolved, defaults to context configuration option. On non-Windows systems ...
Read more >systemd-resolved - ArchWiki
systemd-resolved is a systemd service that provides network name resolution to local applications via a D-Bus interface, the resolve NSS ...
Read more >resolved.conf - Freedesktop.org
These configuration files control local DNS and LLMNR name resolution. ... Initially, the main configuration file in /etc/systemd/ contains commented out ...
Read more >How to persist “systemd-resolve” configuration for a particular ...
The DNS servers contacted are determined from the global settings in ... This question still doesn't have an accepted answer and as I've ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@kwelch
path.join
does the job for me. A snippet from my webpack config:And I’m explicitly using exactly
"1.8.2"
in package.js, with no^
or~
.@pawelrychlik I am trying this with 1.8.2 but it is not working are you using
path.join
orpath.resolve