5d3102e4db
Currently, our underlying test script uses npm rather than yarn to execute the tests. This is awkward, because we use yarn everywhere else in lieu of npm. It turns out that some setups have node available without npm, and in such environments our tests fail with a cryptic ENOENT error. This changes the tests to use yarn instead. Test plan: `yarn test --full` passes. Thanks to @wpank for help uncovering this issue. |
||
|---|---|---|
| .. | ||
| jest | ||
| RemoveBuildDirectoryPlugin.js | ||
| babel.js | ||
| env.js | ||
| paths.js | ||
| polyfills.js | ||
| test.js | ||
| webpack.config.backend.js | ||
| webpack.config.web.js | ||