-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Conversation
Thanks for this! We've intentionally listed the types explicitly (rather than the whole |
Specifying typeroot as "../../node_modules/@types/node", does not include |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This matches typeRoots
documentation, typescript compiles and LSP continues to serve meta. Thanks @sheetalkamat !
Thanks for sharing your understanding! I'm specifically concerned about certain packages needing to exclude some types. For example, @truffle/dashboard includes types for DOM-related things, but other packages would barf if those types got included... and because this is a monorepo, packages were inheriting these browser-land types from I thought (I'll have to go through the package.json files again to refresh myself, I guess. Also, if CI says we're good, then seems like no problem :) |
It's possible that version upgrades since 2019 may have changed some assumptions.
Pickaxe output
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again for opening this!
PR description
Testing instructions
Documentation
doc-change-required
label to this PR if documentation updates are required.Breaking changes and new features
breaking-change
andnew-feature
labels for the appropriate packages.Fixes build breaks with typescript@next per microsoft/TypeScript#53122 (comment) because of incorrect typeRoots