set-function-name
npmv2.0.2TypeScriptSet a function's name property
Adopt with care
set-function-name is usable, with caveats. Last published 933 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- DMaintenance: grade D, Poor — a real concern.
Last published 933 days ago.
- BWeight: grade B, Good.
Pulls in 6 transitive packages, about 94 KB installed (at least — some of the tree is still being crawled).
- ASupply chain: grade A, Excellent.
No install scripts, 2 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 set-function-name 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.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Licenses in the dependency tree
Every license you inherit by installing set-function-name, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >= 0.4
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the set-function-name README.
var setFunctionName = require('set-function-name');
var assert = require('assert');
const obj = {
concise() {},
arrow: () => {},
named: function named() {},
anon: function () {},
};
assert.equal(obj.concise.name, 'concise');
assert.equal(obj.arrow.name, 'arrow');
assert.equal(obj.named.name, 'named');
assert.equal(obj.anon.name, 'anon');
set-function-name 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 |
|---|---|---|---|---|
| set-function-namethis page | 0 | 1 | MIT | 2 years ago |
| set-function-length | 0 | 1 | MIT | 1 day ago |
| functions-have-names | 0 | 5 | MIT | 1 day ago |
| callsites | 136.7M | 1 | MIT | 1 day ago |
| once | 109.6M | 1 | ISC | 1 day ago |
| reusify | 91M | 1 | MIT | 1 day ago |
Dependencies
Declared by set-function-name v2.0.2. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (4)
Dev (31)
Used by
Popular packages that depend on set-function-name.
Relationship graph
Dependencies (left) and dependents (right) of set-function-name.
Frequently installed together
An AST-based pattern checker for JavaScript.
Robustly `.call.bind()` a function
A simple cache for a few of the JS Error constructors.
`Object.getOwnPropertyDescriptor`, but accounts for IE's broken implementation.
Does this JS environment support the `name` property on functions?
string representations of objects in node and the browser
A robust, ES3 compatible, "has own property" predicate.
Release history
No releases in the last two years, typically about 160 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.0.2latest | 2 years ago | 16 KB | MIT |
| 2.0.1 | 3 years ago | 9.9 KB | MIT |
| 2.0.0 | 3 years ago | 9.7 KB | MIT |
| 1.0.0 | 9 years ago | — | ISC |
Overview
set-function-name is an npm package that set a function's name property. It has 1 known dependents in the graph. The latest version is 2.0.2, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need set a function's name property 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 (35 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Frequently asked questions
Should I use set-function-name?
set-function-name is usable, with caveats. Last published 933 days ago.
How do I install set-function-name?
Run `npm install set-function-name` to add set-function-name to your npm project.
How many dependencies does set-function-name have?
set-function-name declares 35 direct dependencies and pulls in 6 packages in total once its runtime tree is resolved totalling about 94 KB on disk.
What license is set-function-name released under?
set-function-name is distributed under the MIT license.
How popular is set-function-name?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on set-function-name.
Is set-function-name still maintained?
The most recent release of set-function-name (v2.0.2) was published 2 years ago.
Does set-function-name run install scripts?
No. set-function-name does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.