Fetch bindings for BuckleScript
npm install bs-fetchLow-level bindings to fetch for BuckleScript.


![Last Commit]()
![Size]()
bs-fetch is intended as a thin layer atop the JS API, upon which more high-level and idiomatic libraries can be made. Once such a library has been established, these bindings will likely be refactored to be even thinner.
``reason`
Js.Promise.(
Fetch.fetch("/api/hellos/1")
|> then_(Fetch.Response.text)
|> then_(text => print_endline(text) |> resolve)
);
`sh`
npm install --save bs-fetch
Then add bs-fetch to bs-dependencies in your bsconfig.json:`js`
{
...
"bs-dependencies": ["bs-fetch"]
}
and reason_examples.re. The source is a single file!fetch is a Web API that isn't available out-of-the-box in Node.js, and will therefore need to be polyfilled. isomorphic-fetch one such polyfill that seems to work well. Just install it via npm and add [%raw "require('isomorphic-fetch')"] to the top of your main file, but be aware that there are some subtle differences and even parts that are missing entirely.
bindings$3
* Bugfix: Response._type was generating _type instead of type
* Breaking: Rename Response._type to Response.type_ to follow the name mangling convention trends$3
* Added AbortController$3
* Fixed Headers.append and Headers.delete. They were missing the return type.$3
* Bumped bs-platform to 5.0.4 to stop compiler from complaining.$3
* Added HeadersInit.makeWithDict so as to be able to make headers in OCaml too
* Require bs-platform >= 3.0.0 due to internal dependency on Js.boolean that has now been removed$3
* Rename Bs_fetch module to Fetch. Bs_fetch` is kept around as an alias for backwards compatibility, but should be considered deprecated.