stackframe
npmv1.3.4TypeScriptJS Object representation of a stack frame
Not recommended for new projects
No — stackframe should not be adopted for new projects. Last published 1557 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1557 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 23 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 4 maintainers, and a contained dependency surface.
- 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 stackframe 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
- Types included
- Install scripts
- None
Quick start
A usage example from the stackframe README.
// Create StackFrame and set properties
var stackFrame = new StackFrame({
functionName: 'funName',
args: ['args'],
fileName: 'http://localhost:3000/file.js',
lineNumber: 1,
columnNumber: 3288,
isEval: true,
isNative: false,
source: 'ORIGINAL_STACK_LINE'
evalOrigin: new StackFrame({functionName: 'withinEval', lineNumber: 2, columnNumber: 43})
});
stackFrame.functionName // => "funName"stackframe vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| stackframethis page | 0 | 1 | MIT | 4 years ago |
| error-stack-parser | 0 | 2 | MIT | 14 days ago |
| http-errors | 168.8M | 7 | MIT | 14 days ago |
| callsites | 158M | 1 | MIT | 14 days ago |
| serialize-error | 32.1M | 2 | MIT | 14 days ago |
| verror | 23.2M | 1 | MIT | 14 days ago |
Dependencies
Declared by stackframe v1.3.4. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (16)
Used by
Popular packages that depend on stackframe.
Relationship graph
Dependencies (left) and dependents (right) of stackframe.
Frequently installed together
Release history
No releases in the last two years, typically about 70 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.3.4latest | 4 years ago | 23 KB | MIT |
| 1.3.3 | 4 years ago | 23 KB | MIT |
| 1.3.2 | 4 years ago | 23 KB | MIT |
| 1.3.1 | 4 years ago | 35 KB | MIT |
| 1.3.0 | 4 years ago | 35 KB | MIT |
| 1.2.1 | 4 years ago | 32 KB | MIT |
| 1.2.0 | 6 years ago | 31 KB | MIT |
| 1.1.1 | 6 years ago | 30 KB | MIT |
| 1.1.0 | 7 years ago | 38 KB | MIT |
| 1.0.4 | 9 years ago | — | MIT |
| 1.0.3 | 9 years ago | — | MIT |
| 1.0.2 | 10 years ago | — | Unlicense |
| 1.0.1 | 10 years ago | — | Unlicense |
| 1.0.0 | 10 years ago | — | SEE LICENSE IN LICENSE |
| 0.3.1 | 11 years ago | — | SEE LICENSE IN LICENSE |
Overview
stackframe is an npm package that jS Object representation of a stack frame. It has 1 known dependents in the graph. The latest version is 1.3.4, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need jS Object representation of a stack frame and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- Large dependency tree (16 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use stackframe?
No — stackframe should not be adopted for new projects. Last published 1557 days ago.
How do I install stackframe?
Run `npm install stackframe` to add stackframe to your npm project.
What license is stackframe released under?
stackframe is distributed under the MIT license.
How popular is stackframe?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on stackframe.
Is stackframe still maintained?
The most recent release of stackframe (v1.3.4) was published 4 years ago.
Does stackframe run install scripts?
No. stackframe does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.