funkpower 57bc4356ab publish as catena-corpus on PyPI and npm ...

Both registries already have a `catena`: an HPE blockchain client on PyPI,
and a JavaScript OOP wrapper at 2.2.0 on npm. Neither is going anywhere, so
the distributions take a name that is free on both.

The Python import is unaffected — a distribution name and a module name are
independent there, so `pip install catena-corpus` still gives `import
catena`, and nothing in the examples or the bindings changes. On npm the
package name is the import specifier, so that one does change: `import
{ chunkMarkdown } from "catena-corpus"`.

The crates keep their own names. `catena` is free on crates.io.

2026-09-21 08:15:26 -04:00

..

src

publish as catena-corpus on PyPI and npm

2026-09-21 08:15:26 -04:00

package.json

publish as catena-corpus on PyPI and npm

2026-09-21 08:15:26 -04:00

tsconfig.json

examples: programs that run, in four languages

2026-09-21 08:12:13 -04:00