npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

rescript-fetch

v0.0.3

Published

a binding for the [Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API).

Downloads

89

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

webbureaucratwebbureaucrat

Keywords

Readme

rescript-fetch

a binding for the Fetch API.

reason for being

It's not easy to justify writing this package when the venerable bs-fetch still exists and works. However, ultimately going forward, I want a fetch binding that meets the following goals:

  • The new, preferred binding for ReScript promises is the rescript-promise package. If I'm writing greenfield code, then that's the binding I want to use.
  • Honestly, I really struggle to read proper OCaml anymore, and I'm sure that goes double for people who never cut their teeth on ReasonML.

breaking changes

My philosophy on breaking changes is that they are inevitable. I try to be nice with semantic versioning and just not go "1.0.0" but if you can't tolerate some light refactoring after an update, you shouldn't add this dependency.

I don't anticipate breaking changes in the underlying Fetch API, but when rescript-promise starts getting shipped with the main ReScript, I do intend to upgrade the promises returned in this package.

Contributing

Please feel free! Open issues or add any missing bindings you find. Do try to follow the style of the existing code.

Since this is just a binding and doesn't have any particular logic on its own, I tend to think this is fairly self-documenting, but feel free to open issues if you have any questions on how the existing code works. (Since there are no highly experienced ReScript developers right now, so there are no stupid questions.)