Skip to content
This repository was archived by the owner on May 29, 2019. It is now read-only.

Weird resource path for files extracted using the plugin #692

Closed
woldner opened this issue Jan 2, 2018 · 1 comment
Closed

Weird resource path for files extracted using the plugin #692

woldner opened this issue Jan 2, 2018 · 1 comment

Comments

@woldner
Copy link

woldner commented Jan 2, 2018

Windows 10
Node v9.2.0

I've created a sample project here-- using the source map example from the sass-loader docs and code from the extract-text-webpack-plugin docs here

With the sample project above I used devtool: "inline-source-map".

Examples of actual resource paths paths

Actual app.scss path is ./src/styles/app.scss

ex1

However after using the extract-text-wepack-plugin to extract the css, the resource path for the extracted file becomes ./src/styles/src/styles/app.scss and the absolute resource path: C:/Users/m51n/source/repos/source-map-path/src/styles/src/styles/app.scss (does not exist)

ex2

When looking at the info from devtoolModuleFilenameTemplate commented here, the resource paths differs from other resource paths after being extracted with the extract-text-webpack-plugin.

Expected

Expected resource path returned by the plugin in this case would be ./src/styles/app.scss and absolute resource path as it exist on disk: C:/Users/m51n/source/repos/source-map-path/src/styles/app.scss

@woldner
Copy link
Author

woldner commented Jan 2, 2018

closing as this is probably not related to the extract-text-webpack-plugin..
i've opened a similar issue with css-loader instead.

webpack-contrib/css-loader#652

@woldner woldner closed this as completed Jan 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant