packages/compiler-cli/integrationtest/package.json

{
  "#1": "We maintain a `package.json` file so that all scripts for the integration test are not",
  "#2": "accidentally treated as ESM when tests run on Windows. On Windows, the scripts are",
  "#3": "not symlinked into a runfile tree/sandbox, so they accidentally get the `type`: `module`",
  "#4": "from the compiler-cli package.json file.",
  "type": "commonjs"
}
test(compiler-cli): fix integration test failing on windows due to missing runfile symlinking (#43431) Currently, some tests in the `compiler-cli/integrationtest` package fail on Windows because there are spec files which are not Bazel-generated. When Bazel runs these tests on Windows, the spec file is resolved to the actual source file (since there is no runfile symlinking/sandboxing). This breaks the execution of the CJS spec file since it resides in th `packages/compiler-cli` source folder which has a `package.json` set to `type: module`. We fix this by adding a `package.json` file for the integration test folder and setting `module` to `commonjs`. PR Close #43431 2021-09-30 17:43:25 +02:00			`{`
			"#1": "We maintain a `package.json` file so that all scripts for the integration test are not",
			`"#2": "accidentally treated as ESM when tests run on Windows. On Windows, the scripts are",`
			"#3": "not symlinked into a runfile tree/sandbox, so they accidentally get the `type`: `module`",
			`"#4": "from the compiler-cli package.json file.",`
			`"type": "commonjs"`
			`}`