-
-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Type errors in TypeScript 5.6 due to lib changes (both in source and declaration files) #352
Comments
|
I don't typically worry about TypeScript version changes, especially not |
Yeah, I should have been more clear: this isn’t just a problem for building, this is a problem that all users of lru-cache would see in e.g.
build is aliased to prepare, which runs tshy, but my point is that I thought that tshy would type check. Do you not type check this package from the CLI or during CI? |
Tshy does type check, but using its own version of typescript that it depends on. |
Due to isaacs/node-lru-cache#352 preventing us from upgrading typescript Causes more warnings about the version being incompatible with what the deps want, unfortunately.
Due to isaacs/node-lru-cache#352 preventing us from upgrading typescript Causes more warnings about the version being incompatible with what the deps want, unfortunately. Attempt 2 with newer yarn, replaces #1904
Due to isaacs/node-lru-cache#352 preventing us from upgrading typescript Causes more warnings about the version being incompatible with what the deps want, unfortunately. Attempt #2 with newer yarn, replacing #1904
Brings in this commit which makes the types valid for TypeScript 5.6 isaacs/node-lru-cache@5ed947d More details: isaacs/node-lru-cache#352
TypeScript 5.6 (currently in RC) includes some changes to builtin iterator types, which causes several of the iterator-returning methods of LRUCache to be unassignable to its
implements Map<K, V>
. For details, see microsoft/TypeScript#58243. To reproduce:As an aside, I noticed that neither
npm run build
nornpm test
seems to type check currently (or at least tshy isn’t reporting the type errors to the console)—is that intended?The text was updated successfully, but these errors were encountered: