Update to todays wasm-pack #151
Conversation
…/webpack-dev-server-3.5.1 Build(deps-dev): Bump webpack-dev-server from 3.3.1 to 3.5.1
Bumps [webpack](https://github.com/webpack/webpack) from 4.31.0 to 4.33.0. - [Release notes](https://github.com/webpack/webpack/releases) - [Commits](webpack/webpack@v4.31.0...v4.33.0)
…/webpack-4.33.0 Build(deps-dev): Bump webpack from 4.31.0 to 4.33.0
Bumps [webpack-dev-server](https://github.com/webpack/webpack-dev-server) from 3.5.1 to 3.7.1. - [Release notes](https://github.com/webpack/webpack-dev-server/releases) - [Changelog](https://github.com/webpack/webpack-dev-server/blob/master/CHANGELOG.md) - [Commits](webpack/webpack-dev-server@v3.5.1...v3.7.1) Signed-off-by: dependabot-preview[bot] <[email protected]>
…/webpack-dev-server-3.7.1 Build(deps-dev): Bump webpack-dev-server from 3.5.1 to 3.7.1
Significant changes to clean things up and improve the user UX
|
I don't think this is quite correct. A lot of apps are designed to be run in the browser, so running the tests in Node will fail. |
|
Ideally this should be fixed in wasm-pack, so we can just run |
|
Well that might be true, however they decided to change the flag from |
|
@dns2utf8 Where did you hear that? |
|
I got an error message when using the command: |
|
@dns2utf8 Yes, that is correct, you must specify at least one of those options, like so: wasm-pack test --headless --chrome
wasm-pack test --headless --firefox
wasm-pack test --headless --safariOr you can combine multiple together: wasm-pack test --headless --chrome --firefox --safariNote that the As for this template specifically, you can use It was setup that way because different people will have different browsers, so that lets you choose which browsers to run the tests in. |
No description provided.