Dandelion Mané 5d3102e4db

Tests use yarn not npm (#1038) ...

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.

2019-01-07 14:38:21 -08:00

..

jest

flow: add typing to Jest transform modules (#790)

2018-09-06 13:30:33 -07:00

babel.js

babel: transform ES6 modules to CommonJS (#766)

2018-09-04 21:47:36 -07:00

env.js

Move repoIdRegistry to core (#992)

2018-11-01 18:11:48 -07:00

paths.js

webpack: remove dynamic import (#982)

2018-11-01 13:24:31 -07:00

polyfills.js

Ensure that flow is used in all js files (#232)

2018-05-07 20:02:19 -07:00

RemoveBuildDirectoryPlugin.js

webpack: empty build dir instead of removing it (#768)

2018-09-04 21:44:09 -07:00

test.js

Tests use yarn not npm (#1038)

2019-01-07 14:38:21 -08:00

webpack.config.backend.js

webpack: expose repo registry at build time (#981)

2018-11-01 12:38:18 -07:00

webpack.config.web.js

core: allow repo ID registry to store metadata (#1003)

2018-11-09 17:28:39 -08:00