-
-
Notifications
You must be signed in to change notification settings - Fork 209
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
[2.0.5] Warnings about missing sourcemap when they are enabled (options.sourceMap
)
#248
Comments
(Emitted value instead of an instance of error) |
@danyim The typo should be fixed on master already, thx 😛 . Can you try without |
@danyim I can't reproduce this in a small local test, could you please setup a small repo for debugging ? |
options.sourceMap
)
Feel free to reopen if still regressions and please provide a small test repo, since I couldn't reproduce this myself |
Hello, Postcss-loader: 2.0.6 I still have the warning "Previous source map found, but options.sourceMap isn't set."
Thank you for your help |
@Janaka-Steph + 'postcss-loader?sourceMap',
'sass-loader?sourceMap' |
@Janaka-Steph I got around this by adding |
Dah! @michael-ciniawsky wins the day! 🌮 🌮 for you. |
No it doesn't work for me :-( |
@Janaka-Steph Here's exactly what I changed in my config to get rid of the warning.
|
Nope :-/
Maybe it is due to bootstrap-loader ? Here is the repo if you want to have a look: https://github.com/asseth/dao1901/tree/develop |
@michael-ciniawsky |
@matthopson That doesn't fix the problem properly. The a source map is needed for production, so by enabling it in development environment, you are increasing the build time, because it has to generate a Source map, which is really not needed, because while developing, your CSS is not minified. So far, the only thing that fixes it for me is moving to |
I'm seeing these warnings:
when my Webpack config explicitly sets the option to true:
Is there something I am misconfiguring? Or is this a bug? Also, "enterily" is typoed in the warning text.
The text was updated successfully, but these errors were encountered: