-
Notifications
You must be signed in to change notification settings - Fork 75
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
Provide source maps support #1
Comments
That's true. Source maps are currently not supported. I'm working on that. |
How long do you think it's gonna take? |
I'm sorry, too much work currently. If anyone is interested, please go ahead :). The code is fairly simple and I can give you support. |
@jhnns I can work on it if you show me where to start. (I'm pretty new to Webpack development though) |
@sentika This is my scss compilation/extraction section of my webpack config file: {
test: /\.scss$/,
use: [
{
loader: 'file-loader',
options: {
name: '[name].css',
context: './src/css/',
outputPath: 'css/',
publicPath: '../'
}
},
{
loader: 'extract-loader'
},
{
loader: 'css-loader',
options: {
sourceMap: true
}
},
{
loader: 'resolve-url-loader'
},
{
loader: 'postcss-loader'
},
{
loader: 'sass-loader',
options: {
sourceMap: true
}
}
]
} And I can see sourcemaps, but instead of separate It's a workaround, not a solution, but at least works. |
Is there any ETA ? |
@jstrimpel I tried to explain it to you how to fix it. On the way explaining it, I found the solution for the problem 😁 Shipped with |
@jhnns Thank you so much! |
There is no source map after using extract. For example in this chain:
style/url!file!extract!css
The text was updated successfully, but these errors were encountered: