In the future, when Ky is more mature, we should add a comparison table to the readme. Like https://github.com/sindresorhus/got#comparison

https://developers.google.com/web/updates/2017/09/abortable-fetch

Currently it is only implemented in Firefox 57 and is coming to other browsers soon.

const controller = new AbortController();
const signal = controller.signal;

setTimeout(() => controller.abort(), 5000);

fetch(url, { signal }).then(response => {
  return response.text();
}).then(text => {
  console.lo

We should have a documentation website, perhaps generated from our readme or the other way around, in order to make it easier for people to learn about Cash and browse its functionalities.

If anybody would like to spend the time to make it it'd be awesome.

Thanx for the great library, but I was unable to get it working from the "examples" in the readme.

The readme does not provide a full working example but just code snippets. It still is not clear which parameter I missed, but I did not get a working sample through hours. :-(

For me https://redstapler.co/split-js-tutorial-website-split-screen-effect/ was very helpful since they provided a si

Isn't just enough to not use babel and etc? Why we need this and ES6 syntax and imports at all. It is just overhead. With that we can just remove babel from deps and they will look more clean.

/cc @developit

I don't know if this is the right place to put this, but I can't think of a better one.
The wiki page on RAM often uses an ellipsis instead of having a description, seemingly with varying meaning.
For example, the 03FFC range. What does it do? I can't seem to find info on it anywhere, and the only thing about it on the page is this:
`| 03FFC | ...

We should probably find the optimal one and use that. Currently it varies by a few bytes each time the build script runs.

We have some tests of critical parts, however, in the CLI we only have 3 tests and we are not covering all the cases. I create this issue in order to improve that.