npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@noetic-tools/memory

v3.1.0

Published

DEPRECATED — renamed to @noetic-tools/context. Thin re-export kept for compatibility.

Readme

@noetic-tools/memory

Deprecated — renamed to @noetic-tools/context.

The memory layer system was renamed to the context layer system. These layers assemble the model's context window — recall, budget allocation, history projection, the item-append pipeline, steering — which is what they are for; "memory" only ever described what a few of them happened to store.

This package is now a thin re-export of @noetic-tools/context and receives no further changes. Everything resolves identically through either package, so nothing breaks by staying here — but new code should not.

Migrating

Change the import specifier:

- import { workingMemory, type MemoryLayer } from '@noetic-tools/memory';
+ import { workingMemoryContext, type ContextLayer } from '@noetic-tools/context';

The old names (MemoryLayer, workingMemory, planMemory, …) survive as deprecated aliases in @noetic-tools/context too, so the specifier change alone is a valid first step.

Most applications never import this package directly — @noetic-tools/core re-exports the whole surface.

License

Apache-2.0