-
Notifications
You must be signed in to change notification settings - Fork 364
CSS Sourcemaps activation in dev mode (1.x) #447
Comments
My original plan was to have it activated via a |
Part of the problem here is that you need to nest under slateTools inside your module.exports, the starter theme had it wrong until a few weeks ago
|
Just to add more detail to this ticket, I'm able to get detailed sourcemaps working by directly editing the dev.js in slate-tools node module with this:
And then also modifying css-loader according to this ticket webpack-contrib/css-loader#717 A couple of things:
|
Also for reference webpack/webpack#6400 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Problem
It would be useful to be able to activate CSS/SCSS sourcemaps in dev mode.
If I go and edit directly webpack.dev.conf.js inside the node_modules the sourcemaps are working fine, but this is only a temporary solution.
If I understand correctly in #394 there is mention that by adding a config object inside slate.config.js it should override the config inside node_modules, but it doesn't seem to work :
Code inside slate.config.js
Could this be ultimately activated using a flag ?
The text was updated successfully, but these errors were encountered: