Jake Bailey
Jake Bailey
Here is a test case that shows a variant of this problem: ```ts // @module: nodenext // @target: esnext // @outDir: ./out // @allowJs: true // @checkJs: true // @noUnusedLocals:...
A workaround for type-only files like this is to not use `module.exports = {}`, but instead write something like `module.exports.nothing = undefined` which instead generates separate declarations rather than an...
This comes down to us not using a diagnostic message in `DoCycle`, and so `TryClearScreen` does not detect the starting message and does not issue the screen clearing codes.
Well, rather, I think the watch mode for non-build-mode is just not using the right messages.
@typescript-bot test it
Enums are in a weird place because early on we thought we could avoid doing const inling, and in general avoid using the checker for them. But we then flipped...
This error is an assignability error, so either they are are trying to assign something _into_ `rmdirSync` (or something based on that), or have multiple `@types/node` packages?
I am not sure we actually support `--noCheck` yet. `--noCheck` is somewhat of a lie, sometimes, and does need to make sure some parts of the checker have been run...
Though, `--noResolve` does complicate it. Maybe this is a case of "no node reuse"?
Do all of your examples involve `as`?