-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Publish VS Code sourcemaps #2863
Comments
Cloned the main branch and built - seeing the source, but not the same files as in the release. I might be reading the code wrong, but it seems...
... is telling gulp-sourcemap to not include the the source map comment for workbench.main, however missing this sounds like Chrome won't know where to get the source from, which would normally I guess be in this missing comment. Is this accurate? |
@ianwesterfield Cool. We've been wanting to put the sourcemaps online for a while now. Let me work on that. |
@joaomoreno Maybe no more need to ship the plugin host sourcemap then? |
👍 |
I was going to look into a possible bug in VS Code, but toggling Developer Tools reveals minified scripts with no apparent source mapping.
I see the use of gulp-sourcemaps in the build scripts, but I've never used it so I'm unsure how to verify it is actually doing it's job or why Chrome isn't parsing them if it is. I'll look deeper into it later on unless I get word back I'm doing something wrong 😄
The text was updated successfully, but these errors were encountered: