Joe Clack

It's impossible to consume your library from a TypeScript project without type declarations. Consuming your library from a TypeScript project ***is*** the use-case. ```ts // today, typescript shows an error...

`bar` is a `string[]`. An array of strings. Can also be written `Array`. Ramda has a DefinitelyTyped package: https://www.npmjs.com/package/@types/ramda i.e. type definitions are provided, just not directly. So it can...

> Then similar ones should be possible to create for `cpsfy` I presume, if anyone likes to do it, I'll be happy to include a link. :) `@types/ramda` actually depends...

You don't need any dependencies. Just a `.d.ts` file. For checking the syntax of the file you can optionally install `typescript` as a development dependency. No runtime dependencies are required....

Having a separate package is not minimalist, it's maximalist. It creates more work for everyone. An API change here, requires communication to maintainers over there, who have to make a...

> Unfortunately, both `ava` and `tape` would not work with `npx` without installation, would they? I see no reason they wouldn't. `npx documentation` works by downloading the `documentation` package from...

Re. Ava and tape: ah, I see - I think you're right. I forgot that the test-runners contained import-able utilities. There might be a very hacky way of doing it...

My personal preference these days is `vitest`, but that's primarily because it makes authoring tests in TypeScript a breeze. Since you don't need that, `jest` is good. The design of...

Reverting to draft to avoid potential merge conflicts with fellow collaborator

I don't understand how to fix the build. The errors seem unrelated to my changes? some help would be much appreciated!