Files
catena/crates/bindings/npm/package.json.in
T
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

27 lines
1.0 KiB
Plaintext

{
"name": "catena-corpus",
"version": "@VERSION@",
"description": "Turn a pile of files into a searchable corpus: chunking, scrubbing, subtitles and rank fusion, as WebAssembly",
"license": "MPL-2.0",
"homepage": "https://git.pumpin.online/funkpower/catena",
"repository": {
"type": "git",
"url": "git+https://git.pumpin.online/funkpower/catena.git"
},
"keywords": ["chunking", "markdown", "subtitles", "retrieval", "corpus", "tokens", "wasm"],
"type": "module",
"types": "./web/catena.d.ts",
"exports": {
".": {
"node": { "types": "./node/catena.d.cts", "default": "./node/catena.cjs" },
"default": { "types": "./web/catena.d.ts", "default": "./web/catena.js" }
},
"./node": { "types": "./node/catena.d.cts", "default": "./node/catena.cjs" },
"./web": { "types": "./web/catena.d.ts", "default": "./web/catena.js" },
"./node/*": "./node/*",
"./web/*": "./web/*",
"./package.json": "./package.json"
},
"files": ["node/", "web/", "README.md", "LICENSE"]
}