-
Notifications
You must be signed in to change notification settings - Fork 499
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
Move --sourcemap
to scripts instead of Invoke-Build
#4707
Conversation
Isn't evanw/esbuild#944 an issue? vscode-powershell/vscode-powershell.build.ps1 Lines 97 to 107 in bf54870
|
The build script adds |
I'm using build watch and not the build script, that's probably why, it happens with "run extension" but not run tests because the file that it uses to run is different for both. Let me think about this tomorrow, I have an idea how to do it better. |
So that they're generated even when using `build-watch`. Double-checked that they're not included in the package (even though they're now generated for release configuration too).
32a097e
to
368bbb9
Compare
@JustinGrote I gotchu. |
--sourcemap
to scripts instead of Invoke-Build
@andyleejordan thanks! I was going to just put it in the watch npm script but as long as it doesn't hurt anything in main (it shouldn't since the tsc source maps shouldn't conflict) I'm good with it there, they take an insignificant amount of additional time to generate. |
PR Summary
ESBuild does not currently generate sourcemaps for debugging. This enables that generation and I verified that
vsce
does not include the sourcemaps when packaging.PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an
x
between the square brackets.Please mark anything not applicable to this PR
NA
.WIP:
to the beginning of the title and remove the prefix when the PR is ready