You can add the plugins as suggested by @Vikramaditya. Then to generate the production build. You have to run the the command NODE_ENV=production webpack –config ./webpack.production.config.js If using babel, you will also need to prefix BABEL_ENV=node to the above command.
You can use dotenv package for this purpose. npm install dotenv –save After installing the package, add this in the top of your config: const webpack = require(‘webpack’); // only add this if you don’t have yet // replace accordingly ‘./.env’ with the path of your .env file require(‘dotenv’).config({ path: ‘./.env’ }); then in plugins … Read more
There is currently a bug when using sourceMap with css-loader. Removing sourceMap from your css loader should fix it. “module”: { “loaders”: [ { “test”: /\.scss$/, “loaders”: [“style”, “css”, “sass?sourceMap”] }, { test: /\.jpg$/, loader: “file-loader” } ] } Issue is related to: https://github.com/webpack/css-loader/issues/296
As the error message says, you need to use absolute path. To get an absolute path for current directory, You can use __dirname to get the current directory and then append dist/js. So it would be something like, output: { path: __dirname + “/dist/js”, // or path: path.join(__dirname, “dist/js”), filename: “bundle.js” } Both will work … Read more
Two things were causing my problems here: module.exports = { entry: ‘./src/index.js’, output: { // For some reason, the `__dirname` was not evaluating and `/public` was // trying to write files to a `public` folder at the root of my HD. path: __dirname + ‘/public’, // Public path refers to the location from the _browser’s_ … Read more
See an entrypoint as the root of a tree that references many other assets like javascript modules, images, templates and so on. When you define more than one entrypoint, you basically split your assets into so called chunks to not have all your code and assets in one single bundle. What I think you want … Read more
You can import the css file on App.vue, inside the style tag. <style> @import ‘./assets/styles/yourstyles.css’; </style> Also, make sure you have the right loaders installed, if you need any.
Webpack doesn’t know to resolve .jsx files implicitly. You can specify a file extension in your app (import App from ‘./containers/App.jsx’;). Your current loader test says to use the babel loader when you explicitly import a file with the jsx extension. or, you can include .jsx in the extensions that webpack should resolve without explicit … Read more
Something like this worked for me. I am guessing this should work for you. Run webpack-dev using this webpack-dev-server –host 0.0.0.0 –port 80 And set this in webpack.config.js entry: [ ‘webpack-dev-server/client?http://0.0.0.0:80’, config.paths.demo ] Note If you are using hot loading, you will have to do this. Run webpack-dev using this webpack-dev-server –host 0.0.0.0 –port 80 … Read more
Original Answer I finally found the answer, in this RFC about CORS-RFC1918 from a Chrome-team member. To sum it up, Chrome has implemented CORS-RFC1918, which prevents public network resources from requesting private-network resources – unless the public-network resource is secure (HTTPS) and the private-network resource provides appropriate (yet-undefined) CORS headers. There’s also a Chrome flag … Read more