Remco Haszing
Remco Haszing
I wouldn’t say a user _can_ use a type annotation. I would say a user _should_ use a type annotation. The `satisfies` keyword narrows the inferred type, but it doesn’t...
A semi-related miscellaneous tip: Since ESLint supports JSX by default, replace `@types/estree` with `@types/estree-jsx`. This augments `@types/estree` with JSX node types and re-exports everything. It’s a drop-in replacement.
Apparently this doesn’t work with all Node.js versions we support.
According to the TypeScript handbook, [ambient modules](https://www.typescriptlang.org/docs/handbook/modules/reference.html#ambient-modules) can be declared in script files, not in modules. The following works: ```jsonc // tsconfig.json { "compilerOptions": { "module": "preserve", "strict": true }...
Sadly no. It’s possible to force a file into module mode by adding `export {}`, but not the other way around. You recommendation to force module detection does make sense,...
Nice, I like it. But that doesn’t remove `vite-env.d.ts` from the [_IntelliSense for TypeScript_](https://vite.dev/guide/env-and-mode#intellisense-for-typescript) section.
This also uncovers that rerendering changes text selections. When selecting text, the selection ranges within the wrapped viewport are saved. When line wrapping changes, these ranges are restored. So for...
I rebased onto main and added back support for line injected text. I tested the changes in the playground introduced in #249616 with the following code: ```ts /*--------------------------------------------------------------------------------------------- * Copyright...
> The approach we have taken is to use the DomLineBreaksComputer class when we detect there are variable font sizes on a line and inside of this class to render...