-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 maps broken in 10.2.0 #1264
Comments
Seems like it's a problem with exorcist's mold-source-map using an older convert-source-map. I think it's not recognizing Can you try updating their convert-source-map to see if it fixes it? |
Ah yeah, looking at the regex, that would make sense. |
@zertosh thanks for clarification. Opened issue in convert-source-map repo, but I'm not sure that this issue could be closed now as exorcist is "official" way for managing source maps with browserify and it broken with latest browserify release. |
@playpauseandstop I opened thlorenz/mold-source-map#6 in mold-source-map to fix the problem. When/if that gets merged and published, depending on the version, it might then require yet another PR in exorcist. |
I merged the commit and updated exorcist as well. |
Thanks, guys! Confirmed that now everything works as expected. |
Looks like update browser-pack to ^5.0.0 broke source maps management by exorcist.
file.js:
But after upgrade browserify to 10.2.0 exorcist doesn't understand source map generated by browserify,
Source file bundled as,
So
//# sourceMappingURL...
contains in bundle, but couldn't be recognized by exorcist.The text was updated successfully, but these errors were encountered: