You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
first off, thanks for making this project! It's a nice wrapper around the native fetch API and now definitely my favorite tool for doing http requests from the browser.
I see the project was initiated over 3 years ago and has grown healthily since. With almost 675k weekly downloads (congratulations!) it would be nice to see a "1.0.0" release.
Personally when considering packages for use, this is one of the factors I look at, as I expect https://semver.org/ to be followed and a major version >0 communicates an intent to keep the public API stable, which signifies to responsible developers that it is safe for adoption. For a relatively small package like Ky, that would not seem terribly difficult to achieve.
If you don't intend to do it now, can you define a project, milestone or issue with the things you want to see in the lib before marking it officially stable?
The text was updated successfully, but these errors were encountered:
We also need to wait for TypeScript 4.7 as it brings ESM support. The reason we have to wait is so that we can ensure we have proper ESM config for TypeScript that will not require any breaking changes later on.
Hi,
first off, thanks for making this project! It's a nice wrapper around the native fetch API and now definitely my favorite tool for doing http requests from the browser.
I see the project was initiated over 3 years ago and has grown healthily since. With almost 675k weekly downloads (congratulations!) it would be nice to see a "1.0.0" release.
Personally when considering packages for use, this is one of the factors I look at, as I expect https://semver.org/ to be followed and a major version >0 communicates an intent to keep the public API stable, which signifies to responsible developers that it is safe for adoption. For a relatively small package like Ky, that would not seem terribly difficult to achieve.
If you don't intend to do it now, can you define a project, milestone or issue with the things you want to see in the lib before marking it officially stable?
The text was updated successfully, but these errors were encountered: