-
Notifications
You must be signed in to change notification settings - Fork 30.5k
[node] Add fetch types #66824
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
[node] Add fetch types #66824
Changes from all commits
add2448
58f95bd
ab70b4c
d73fd65
ba59420
b6a3e0f
6d199df
491c162
e942e80
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,11 +1,11 @@ | ||
| import hidefile = require("hidefile"); | ||
|
|
||
| hidefile.hide("./", () => {}); // $ExpectType void | ||
| hidefile.hideSync("./"); // $ExpectType string | Buffer | URL | ||
| hidefile.hideSync("./"); // $ExpectType string | Buffer | URL || string | URL | Buffer | ||
| hidefile.isDotPrefixed("./"); // $ExpectType boolean | ||
| hidefile.isHidden("./", () => {}); // $ExpectType void | ||
| hidefile.isHiddenSync("./"); // $ExpectType boolean | ||
| hidefile.reveal("./", () => {}); // $ExpectType void | ||
| hidefile.revealSync("./"); // $ExpectType string | Buffer | URL | ||
| hidefile.revealSync("./"); // $ExpectType string | Buffer | URL || string | URL | Buffer | ||
| hidefile.shouldBeHidden("./", () => {}); // $ExpectType void | ||
| hidefile.shouldBeHiddenSync("./"); // $ExpectType boolean |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,5 +3,8 @@ | |
| "types": "index", | ||
| "typesVersions": { | ||
| "<=4.8": { "*": ["ts4.8/*"] } | ||
| }, | ||
| "dependencies": { | ||
| "undici-types": "~5.25.1" | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is the first version of undici-types available, but it reflects a newer minor version than is actually included in Node.js so far. It sounded from nodejs/undici#2261 (comment) like we will be able to wait on a new Node.js version comes out containing undici 5.25 and bump the
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, I don't think there's much of an issue shipping this now and then getting synced up later. If there's an actual issue (some bug or whatever), then just tell me exactly which version you want me to publish and I'll manually go a publish the
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Kinda concerned about the impact of this on users of
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you elaborate? This isn’t undici, just undici-types.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. All those patch versions are identical, minus tiny bugfixes for other issues.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. More curious if we should make this I'm not sure if I'm overstating the issue of if this is simply not a concern.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, mainly I assume this is a question of "what if there are multiple types packages in a project", where previously
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The downside to loosening the range is indicating to a Node.js 20.3.X user (for example) that they have access to undici features that they actually don’t. undici just recently added support for HTTP2, so using a On the other hand, I think you’re just automatically screwed if you have two |
||
| } | ||
| } | ||
Uh oh!
There was an error while loading. Please reload this page.