integration/injectable-def/run_test.sh

#!/bin/bash
set -e -x

rm -rf node_modules/lib1_built node_modules/lib2_built dist/

ngc -p tsconfig-lib1.json
cp src/package-lib1.json node_modules/lib1_built/package.json

ngc -p tsconfig-lib2.json
cp src/package-lib2.json node_modules/lib2_built/package.json

ngc -p tsconfig-app.json

# Note: The src `package.json` needs to be moved to `dist` so that the main file can
# be loaded as ESM. TypeScript does not yet support emitting `.mjs` files. Also we do
# not want to set the module type at the top-level `package.json` of this test as this
# breaks the JS files generated by `rules_nodejs` for actually running the integration test runner.
cp src/package.json dist/

node ./dist/src/main.js
test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) Switches the integration tests form Puppeteer/webdriver-manager to the Bazel-managed Chromium/Chromedriver. This is now possible with the new integration test rule for which we can consult the `dev-infra/bazel/browsers` toolchain and setup environment variables. This has been configured already in a previous commit. This commit also includes some additional small cleanups necessary for the new integration test rule: * The `test.sh` scripts have been renamed as they would conflict with the `test.sh` scripts generated by the integration test rule. Previously this was not an issue because tests were declared at a higher-level. As mentioned though this has other downsides and it is trivial to rename the file. * Related to the point above, since tests are now declared witin the actual test folder (for perf e.g.), `package.json` files setting `"type": "module"` will accidentally cause the `nodejs_test`-generated files to be considered ESM. This is not correct and likely needs to be fixed upstream in `rules_nodejs` where explicit `.cjs` extensions should be used. This is only happening once in the `injectable-def` test so it is acceptable doing that for now. PR Close #44238 2021-11-20 17:23:07 +01:00			`#!/bin/bash`
			`set -e -x`

			`rm -rf node_modules/lib1_built node_modules/lib2_built dist/`

			`ngc -p tsconfig-lib1.json`
			`cp src/package-lib1.json node_modules/lib1_built/package.json`

			`ngc -p tsconfig-lib2.json`
			`cp src/package-lib2.json node_modules/lib2_built/package.json`

			`ngc -p tsconfig-app.json`

			# Note: The src `package.json` needs to be moved to `dist` so that the main file can
			# be loaded as ESM. TypeScript does not yet support emitting `.mjs` files. Also we do
			# not want to set the module type at the top-level `package.json` of this test as this
			# breaks the JS files generated by `rules_nodejs` for actually running the integration test runner.
			`cp src/package.json dist/`

			`node ./dist/src/main.js`