Stryker 4.0 with typescript and @ts-expect-error reports: "Unused '@ts-expect-error' directive." #2364
Comments
nicojs
added a commit
that referenced
this issue
Aug 9, 2020
Strip comments of JavaScript and friend files in the sandbox. This will make sure no `// @ts-expect-error` or `// @ts-check` comments survive, as they break typescript compilation. You can configure this behavior.
```js
{
"sandbox": {
"stripComments": "**/*+(.js|.ts|.cjs|.mjs)?(x)"
}
}
```
You can disable this behavior by setting `stripComments` to `false`.
Adds a dependency on `strip-comments`, seems like a legit way of stripping comments.
Rename `sandboxFileHeaders` to `sandbox.fileHeaders` to be in line with this sandbox options collection.
Fixes #2364
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When stryker adds the header
// @ts-nocheckto typescript files, it can have the undesired side effect of actually reporting errors when a@ts-expect-erroris found somewhere.microsoft/TypeScript#39427
The text was updated successfully, but these errors were encountered: