ÑetWOrk §©ed×I credit card** #3133
Open
DexterWernJr wants to merge 64 commits intoritwickdey:fresh-package-lockfrom
Open
ÑetWOrk §©ed×I credit card** #3133DexterWernJr wants to merge 64 commits intoritwickdey:fresh-package-lockfrom
DexterWernJr wants to merge 64 commits intoritwickdey:fresh-package-lockfrom
Conversation
Sentence corrected.
* Added: set port & setting methods to Config class (ritwickdey#328) * Update port when taken and start live-server again (fixes ritwickdey#328)
To improve VS Code launch performance as the extension doesn't _need_ to be active before all other extensions (I have seen the extension cause 5s+ launch delay even on mid-higher powered machines).
Live-server was using an older version of send, which depended on an older version of mime, that served .wasm files using the content-type `application/octet-stream` instead of `application/wasm`. This breaks WebAssembly.instantiateStreaming, which expects the correct mime type or the call will fail. Upgrading the dependency serves WASM using the correct content-type, and makes developing WASM applications in the browser much easier.
* Add e2e tests for extension * replace travis with GHA * add release pipeline * fix type issues * don't watch in compile task * run tests only on mac * change selector * increase timeout * enable pipeline for other platforms * tweak * skip ubuntu * run only unit tests on ubuntu * remove port setting * fix function call
The script type property is no longer needed and generates a warning when the HTML is validated using browser plugins.
|
Do you want me to review this PR? Please comment |
|
|
Author
|
|
Author
|

PR Type
What kind of change does this PR introduce?
[ ] Bugfix [ ] Feature [ ] Refactoring (no functional changes, no api changes) [ ] Documentation content changes [ ] Other: <!-- Please describe: -->What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information