memory-pager
npmv1.5.0Access memory using small fixed sized buffers
Not recommended for new projects
No — memory-pager should not be adopted for new projects. Last published 2800 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 2800 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 7.9 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding memory-pager to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the memory-pager README.
var pager = require('paged-memory')
var pages = pager(1024) // use 1kb per page
var page = pages.get(10) // get page #10
console.log(page.offset) // 10240
console.log(page.buffer) // a blank 1kb bufferDependencies
Declared by memory-pager v1.5.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (2)
Used by
Popular packages that depend on memory-pager.
Relationship graph
Dependencies (left) and dependents (right) of memory-pager.
Release history
No releases in the last two years, typically about 1 day apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.5.0latest | 7 years ago | 7.9 KB | MIT |
| 1.4.0 | 7 years ago | 7.3 KB | MIT |
| 1.3.1 | 7 years ago | 7.1 KB | MIT |
| 1.3.0 | 7 years ago | 7.1 KB | MIT |
| 1.2.0 | 7 years ago | 6.8 KB | MIT |
| 1.1.0 | 9 years ago | — | MIT |
| 1.0.3 | 9 years ago | — | MIT |
| 1.0.2 | 9 years ago | — | MIT |
| 1.0.1 | 9 years ago | — | MIT |
| 1.0.0 | 9 years ago | — | MIT |
Overview
memory-pager is an npm package that access memory using small fixed sized buffers. It has 1 known dependents in the graph. The latest version is 1.5.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need access memory using small fixed sized buffers and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
- Lean dependency tree (2 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use memory-pager?
No — memory-pager should not be adopted for new projects. Last published 2800 days ago.
How do I install memory-pager?
Run `npm install memory-pager` to add memory-pager to your npm project.
What license is memory-pager released under?
memory-pager is distributed under the MIT license.
How popular is memory-pager?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on memory-pager.
Is memory-pager still maintained?
The most recent release of memory-pager (v1.5.0) was published 7 years ago.
Does memory-pager run install scripts?
No. memory-pager does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.