rustwasm/wasm-bindgen
1
0
Fork 0
mirror of https://github.com/rustwasm/wasm-bindgen.git synced 2024-11-24 14:42:35 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity
45d25ebdf0
wasm-bindgen/package.json

21 lines
493 B
JSON
Raw Normal View History

Don't run `npm install` during tests Instead add a `package.json` and use `yarn run`.
2018-03-03 01:20:05 +03:00
{
"license": "MIT",
Fix tests by pinning versions of webpack (#219) Looks like a newer version of webpack has broken tests, so let's use package-lock.json to pin to an older version while we wait for a fix.
2018-06-01 21:42:59 +03:00
"scripts": {
Headless browser testing infrastructure (#371) * tests: Add newlines between impl methods for Project * WIP headless browser testing with geckodriver and selenium * Get some more of headless testing working * Extract `console.log` invocations and print them from the console * Ship the error message from an exception from the browser back to the command line * Cleanup some "if headless" and `else` branches * Fix killing `webpack-dev-server` in the background with `--watch-stdin` * Fix path appending logic for Windows * Always log logs/errors in headless mode * Install Firefox on Travis * Don't duplicate full test suite with `yarn` No need to run that many tests, we should be able to get by with a smoke test that it just works. * headless tests: Move `run-headless.js` to its own file and `include_str!` it * Run `rustfmt` on `tests/all/main.rs` * guide: Add note about headless browser tests and configuration * test: Log WASM_BINDGEN_FIREFOX_BIN_PATH in run-headless.js * TEMP only run add_headless test in CI * Add more logging to headless testing * Allow headless tests to run for 60 seconds before timeout * TEMP add logging to add_headless test * Fix headless browser tests * Another attempt to fix Travis * More attempts at debugging * Fix more merge conflicts * Touch up an error message * Fixup travis again * Enable all travis tests again * Test everything on AppVeyor
2018-07-05 17:22:01 +03:00
"run-webpack": "webpack",
"run-webpack-dev-server": "webpack-dev-server",
"run-geckodriver": "geckodriver"
Fix tests by pinning versions of webpack (#219) Looks like a newer version of webpack has broken tests, so let's use package-lock.json to pin to an older version while we wait for a fix.
2018-06-01 21:42:59 +03:00
},
Don't run `npm install` during tests Instead add a `package.json` and use `yarn run`.
2018-03-03 01:20:05 +03:00
"devDependencies": {
"@types/node": "^9.4.6",
Headless browser testing infrastructure (#371) * tests: Add newlines between impl methods for Project * WIP headless browser testing with geckodriver and selenium * Get some more of headless testing working * Extract `console.log` invocations and print them from the console * Ship the error message from an exception from the browser back to the command line * Cleanup some "if headless" and `else` branches * Fix killing `webpack-dev-server` in the background with `--watch-stdin` * Fix path appending logic for Windows * Always log logs/errors in headless mode * Install Firefox on Travis * Don't duplicate full test suite with `yarn` No need to run that many tests, we should be able to get by with a smoke test that it just works. * headless tests: Move `run-headless.js` to its own file and `include_str!` it * Run `rustfmt` on `tests/all/main.rs` * guide: Add note about headless browser tests and configuration * test: Log WASM_BINDGEN_FIREFOX_BIN_PATH in run-headless.js * TEMP only run add_headless test in CI * Add more logging to headless testing * Allow headless tests to run for 60 seconds before timeout * TEMP add logging to add_headless test * Fix headless browser tests * Another attempt to fix Travis * More attempts at debugging * Fix more merge conflicts * Touch up an error message * Fixup travis again * Enable all travis tests again * Test everything on AppVeyor
2018-07-05 17:22:01 +03:00
"eslint": "^5.0.1",
"geckodriver": "^1.11.0",
"selenium-webdriver": "^4.0.0-alpha.1",
Migrate from `rollup` to `webpack` in tests Building on the previous commit to invoke not invoke `npm install` this takes the commit a step further (to hopefully fix some races) to use Webpack's native bundled wasm support. It turns out the circular dependencies between the wasm module and the module using it wasn't quite working out so a number of imports had to be tweaked, but otherwise it's a nice transition where we don't have to base64 encode anything in tests any more!
2018-03-03 06:20:14 +03:00
"ts-loader": "^4.0.1",
"typescript": "^2.7.2",
feat: bump webpack
2018-06-06 11:07:02 +03:00
"webpack": "^4.11.1",
Update js formatting
2018-06-15 20:55:37 +03:00
"webpack-cli": "^2.0.10",
Headless browser testing infrastructure (#371) * tests: Add newlines between impl methods for Project * WIP headless browser testing with geckodriver and selenium * Get some more of headless testing working * Extract `console.log` invocations and print them from the console * Ship the error message from an exception from the browser back to the command line * Cleanup some "if headless" and `else` branches * Fix killing `webpack-dev-server` in the background with `--watch-stdin` * Fix path appending logic for Windows * Always log logs/errors in headless mode * Install Firefox on Travis * Don't duplicate full test suite with `yarn` No need to run that many tests, we should be able to get by with a smoke test that it just works. * headless tests: Move `run-headless.js` to its own file and `include_str!` it * Run `rustfmt` on `tests/all/main.rs` * guide: Add note about headless browser tests and configuration * test: Log WASM_BINDGEN_FIREFOX_BIN_PATH in run-headless.js * TEMP only run add_headless test in CI * Add more logging to headless testing * Allow headless tests to run for 60 seconds before timeout * TEMP add logging to add_headless test * Fix headless browser tests * Another attempt to fix Travis * More attempts at debugging * Fix more merge conflicts * Touch up an error message * Fixup travis again * Enable all travis tests again * Test everything on AppVeyor
2018-07-05 17:22:01 +03:00
"webpack-dev-server": "^3.1.4",
"babel-eslint": "^8.2.5"
Don't run `npm install` during tests Instead add a `package.json` and use `yarn run`.
2018-03-03 01:20:05 +03:00
}
}
Reference in New Issue Copy Permalink