-
-
Notifications
You must be signed in to change notification settings - Fork 601
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
Match webpack sourcemap relative paths #1219
Match webpack sourcemap relative paths #1219
Conversation
@evilebottnawi thanks for the tip |
Yep, easy to fix, update snapshot too |
c8e9859
to
2a41281
Compare
Adjust source path to match the way webpack generates sourcemaps for js. This makes css and js sources appear in the same directory when using sourcemaps in chrome. Fixes webpack-contrib#1218.
2a41281
to
00d2c29
Compare
Is it not loading my snapshot changes? |
Give me minute on fixing tests |
Let's merge as is and I will fix tests in other PR, want to fix it ASAP |
I'm really confused by why the tests are failing, it seems like linux is getting a different contenthash than on my mac |
but previously they were both getting the same hash |
hash is other because we change sources, so link on source maps changed also, so hash different, don't worry, all is fine |
@evilebottnawi caused by merge conflict in webpack-contrib#1219
I tried in #1221 but it still fails idk |
This PR contains a:
Motivation / Use-Case
Adjust source path to match the way webpack generates sourcemaps
for js. This makes css and js sources appear in the same directory
when using sourcemaps in chrome.
Fixes #1218.
Breaking Changes
Additional Info