For users who have encountered a similar problem, there are steps that I’ve done to get it working, I’m not sure that this equilibrium way. npm install file-loader –save add import ‘leaflet/dist/leaflet.css’; in main app.js change webpack.config.js by following way: add css-loader to get rid of SyntaxError: Unexpected token . and next add file-loader and … Read more
The CSS @import path <url> is usually relative to the current working directory. So using the prefix ~ at the start of the path tells Webpack’s css-loader to resolve the import “like a module”, starting from the node_modules directory. What that means is that if you have a node module called normalize installed, and you … Read more
TL;DR Use absolute paths to your assets (including your complete hostname) by setting your output.publicPath to e.g. “http://example.com/assets/“. The problem The problem is the way that URLs are resolved by Chrome when they’re parsed from a dynamically loaded CSS blob. When you load the page, the browser loads your Webpack bundle entry JavaScript file, which … Read more