Repository navigation
pointers: drop the Node util type from published declarations - #376
Merged
Merged
Conversation
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Data.inspectand itsutil.inspect.customhook typed their options asutil.InspectOptionsStylized, so the published.d.tsimported Node'sutiltypes. Newer@types/nodeversions no longer export that name, and consumers that type-check withskipLibCheck: falsegot errors (PR #374 pins@types/node@20in its consumer check to work around it). The options are now a small local interface (stylizeanddepth) and theinspectargument a structural function type, so the declarations no longer reference Node. Runtime output is unchanged. I packed the package and type-checked a consumer withskipLibCheck: falseagainst@types/node20 and 26 (latest), and with no@types/node(with thedomlib forconsole): all pass.