</>PackageGraphPackageGraph

stackframe

npmv1.3.4TypeScript

JS 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.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

23 KB
Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

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"
Example truncated — see the full README.

stackframe vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
stackframethis page01MIT4 years ago
error-stack-parser02MIT14 days ago
http-errors168.8M7MIT14 days ago
callsites158M1MIT14 days ago
serialize-error32.1M2MIT14 days ago
verror23.2M1MIT14 days ago

Dependencies

Declared by stackframe v1.3.4. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (16)

eslint ^8.17.0jasmine ^4.1.0jasmine-core ^4.1.1karma ^6.3.20karma-chrome-launcher ^3.1.1karma-coverage ^2.2.0karma-coveralls ^2.1.0karma-firefox-launcher ^2.1.2karma-ie-launcher ^1.0.0karma-jasmine ^4.0.2karma-opera-launcher ^1.0.0karma-phantomjs-launcher ^1.0.4karma-safari-launcher ^1.0.0karma-sauce-launcher ^4.3.6karma-spec-reporter ^0.0.34uglify-es ^3.3.9

Used by

Popular packages that depend on stackframe.

Relationship graph

Dependencies (left) and dependents (right) of stackframe.

error-stack-parserstackframe
stackframe dependencies dependents

Frequently installed together

Release history

No releases in the last two years, typically about 70 days apart.

Recent versions of stackframe
VersionPublishedSizeLicense
1.3.4latest4 years ago23 KBMIT
1.3.34 years ago23 KBMIT
1.3.24 years ago23 KBMIT
1.3.14 years ago35 KBMIT
1.3.04 years ago35 KBMIT
1.2.14 years ago32 KBMIT
1.2.06 years ago31 KBMIT
1.1.16 years ago30 KBMIT
1.1.07 years ago38 KBMIT
1.0.49 years agoMIT
1.0.39 years agoMIT
1.0.210 years agoUnlicense
1.0.110 years agoUnlicense
1.0.010 years agoSEE LICENSE IN LICENSE
0.3.111 years agoSEE 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

Keywords

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.