-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable CSS sourcemaps in development #590
Comments
Sounds perfectly reasonable. I would expect Webpack to already do it in DEV mode, does it not? Do you know why? |
This is what I'm seeing ATM but I couldn't tell you why it's happening other than the config not being in place: |
@JaKXz FYI: Relative paths in source maps are buggy and you need to use an absolute public path which includes the server URL. Read more here. Also, shall we use EDIT: Let me know if you need help. |
Going to close since #591 didn’t work out, and I don’t know how else to implement this. |
@gaearon it should probably be left open in that case... right? |
If you know of any possible alternative solution, sure. I’m just not aware of any. |
I got CSS sourcmaps and hot reloading working by following @mareksuscak's advice of changing my css loader in the webpack config to the following: { test: /.css$/, loader: 'style!css?sourceMap!postcss' }, And I can't complain about FOUC (flash of unstyled content) - so all good for development! Hope that may help someone here! 😎 |
as @skaltenegger wrote the config for webpack 2 is
|
Hi! Firstly, of course, thank you for this amazing project! 👏
I've seen the comments on sourcemaps: #109, #139, #494, #343, etc. but didn't see one about enabling CSS sourcemaps. I thought I'd make a PR first but I wanted to discuss first and get to grips with this repo structure.
Since there aren't breakpoints to worry about, this could be a very simple enhancement, e.g:
where
const isProduction = process.env.NODE_ENV === 'production'
. Apologies if I am duplicating / creating noise, I thought I'd searched thoroughly.The text was updated successfully, but these errors were encountered: