Repository navigation
Releases: Particle-Academy/prism-memory-ts
Release list
v0.2.0
v0.2.0 - Node 22 is the floor
Breaking changes: the declared Node floor moves from 20 to 22. Node 20
reached end of life on 2026-04-30, and engines >=20 told consumers that running
there was sanctioned. Be exact about what this does: npm checks engines and
emits EBADENGINE, but it is a WARNING and the install still proceeds. It is a
refusal only where you set engine-strict=true; pnpm refuses by default. No
source changed, so the code would most likely still run on Node 20 -- what
changed is that it is no longer claimed to.
Tested on Node 22, 24 and 26, on Linux and Windows.
This release adds a README. The package has been on npm with no README
at all, so its page showed nothing you could read before installing it.
Every TypeScript example in it is typechecked against the package's own source
rather than written from reading it. That caught four wrong examples before
release -- an interface method that does not exist, a required field left out,
a wrong argument shape, and a missing import. One claim was not just wrong but
backwards, describing a protection the code does not provide; it now states the
actual limit instead.
v0.1.0
v0.1.0 - memory and vector storage for the TypeScript port
@particle-academy/prism-memory provides conversation memory and vector storage.
The embedder is injected, so the whole surface runs with no network and no API
key. That is the design, not a test affordance.
CONFORMANCE. A vector-storage corpus runs the same fixture through all three
languages. Writing it found G-22, fixed the same day.
Filter keys are validated rather than trusted. A key containing -> used to
match nothing silently, which is the failure mode where a query looks like it
ran and quietly answers about nothing.
This is the first published version, and 0.1.0 is meant literally: a focused,
working slice rather than a 1.0 in disguise.
It is published from CI through npm trusted publishing, with a provenance
attestation you can verify. The 0.0.0 that claimed this name was hand-published
and carries none, which is exactly why it was burned rather than used.