Skip to content
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

source-map resource urls coming out strange #231

Closed
DBosley opened this issue May 9, 2017 · 2 comments
Closed

source-map resource urls coming out strange #231

DBosley opened this issue May 9, 2017 · 2 comments

Comments

@DBosley
Copy link

DBosley commented May 9, 2017

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
Using postcss-loader (only using autoprefixer plugin, no extra configurations) combined with sass-loader, css-loader, and style-loader causes the resource URL for sourcemaps to be strange:

example: http://imgur.com/a/R73hV
scss loader config

{
          test: /\.scss$/,
          use: [{
              loader: 'style-loader',
              options: {
                sourceMap: true,
              }
            },
            {
              loader: 'css-loader',
              options: {
                sourceMap: true,
              }
            },
            {
              loader: 'postcss-loader',
              options: {
                sourceMap: true,
                //parser: require('postcss-scss'),
              }
            },
            {
              loader: 'sass-loader',
              options: {
                includePaths: [
                  './src/styles/bootstrap',
                  './src/styles/partials'
                ],
                sourceMap: true,
              }
            },
          ],
          include: [helpers.root('src', 'styles')]
        }

What is the expected behavior?
relative urls for sourcemaps, or at least only one absolute url

Please mention other relevant information such as your webpack version, Node.js version and Operating System.
webpack: 2.5.1
node: 6.10.3
windows 10

@DBosley
Copy link
Author

DBosley commented May 9, 2017

This issue seems to affect multiple loaders. Posted the same issue on all affected loaders:
webpack-contrib/css-loader#529
webpack-contrib/sass-loader#451
#231
webpack-contrib/postcss-loader#224

@alexander-akait
Copy link
Member

Not related to style-loader, feel free to reopen if after merge webpack-contrib/css-loader#532 error still exists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants