-
Notifications
You must be signed in to change notification settings - Fork 511
Bundle the extension #3555
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
Bundle the extension #3555
Conversation
Wow, so this is really annoying. The tooling is absolutely not ready for tests yet. |
1ec5b76
to
956320d
Compare
@rjmholt and @SeeminglyScience please test this (and especially the launch configurations). Everything seems to be working right but it wasn't trivial. |
While we need to bundle the extension code with `eslint` we still have to use `tsc` for the tests, which is annoying. This also fixes are (already broken) VS Code launch tasks!
Since bundling produces a single (bundled) file at `out/main.js` all the relative paths that expected `out/src/...` needed to drop one set of `../` to be correct. We cannot emit the bundled extension to `out/src/main.js` because, as mentioned previously, we still must transpile everything for the unit tests, so `out/src/` is already full.
It's still 64-bit just not `x64`.
956320d
to
82c120d
Compare
Also filed #3561 as a next step. |
// NOTE: The TypeScript compiler is only used for building the tests (and | ||
// the sources which the tests need). The extension is built with `esbuild`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this file configure the typescript compiler rather than esbuild
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, T(ype)S(cript)config.json. While esbuild
supports transpiling typescript to javascript, it does not do any sort of type checking etc., and it also will only produce a bundled file. So we still need tsc
around to type-check the sources and transpile the test code.
This uses
esbuild
as outlined in the VS Code docs to bundle the PowerShell extension.Resolves #2450.