functions-have-names
npmv1.2.3Does this JS environment support the `name` property on functions?
Not recommended for new projects
No — functions-have-names should not be adopted for new projects. Last published 1604 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1604 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 16 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 functions-have-names 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 functions-have-names README.
var functionsHaveNames = require('functions-have-names');
var assert = require('assert');
assert.equal(functionsHaveNames(), true); // will be `false` in IE 6-8functions-have-names 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 |
|---|---|---|---|---|
| functions-have-namesthis page | 0 | 5 | MIT | 4 years ago |
| set-function-name | 0 | 1 | MIT | 1 day ago |
| function-bind | 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 functions-have-names v1.2.3. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (7)
Used by
Popular packages that depend on functions-have-names.
Node's event emitter for all engines.
ES2015-compliant shim for Object.is - differentiates between -0 and +0
string representations of objects in node and the browser
ES6 spec-compliant RegExp.prototype.flags shim.
Set a function's name property
Relationship graph
Dependencies (left) and dependents (right) of functions-have-names.
Frequently installed together
An AST-based pattern checker for JavaScript.
Robustly `.call.bind()` a function
string representations of objects in node and the browser
A simple cache for a few of the JS Error constructors.
Array#isArray for older browsers
Modern Buffer API polyfill without footguns
the most correct and second fastest glob implementation in JavaScript
Determine if the JS environment has `Symbol.toStringTag` support. Supports spec, or shams.
A robust, ES3 compatible, "has own property" predicate.
The semantic version parser used by npm.
`Object.getOwnPropertyDescriptor`, but accounts for IE's broken implementation.
Set a function's name property
Release history
No releases in the last two years, typically about 91 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.2.3latest | 4 years ago | 16 KB | MIT |
| 1.2.2 | 5 years ago | 13 KB | MIT |
| 1.2.1 | 6 years ago | 10 KB | MIT |
| 1.2.0 | 6 years ago | 18 KB | MIT |
| 1.1.1 | 7 years ago | 16 KB | MIT |
| 1.1.0 | 7 years ago | 16 KB | MIT |
| 1.0.0 | 7 years ago | 14 KB | MIT |
Overview
functions-have-names is an npm package that does this JS environment support the `name` property on functions?. It has 5 known dependents in the graph. The latest version is 1.2.3, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need does this JS environment support the `name` property on functions? 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).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use functions-have-names?
No — functions-have-names should not be adopted for new projects. Last published 1604 days ago.
How do I install functions-have-names?
Run `npm install functions-have-names` to add functions-have-names to your npm project.
What license is functions-have-names released under?
functions-have-names is distributed under the MIT license.
How popular is functions-have-names?
npm does not publish download counts. Within PackageGraph's crawl, 5 known packages depend on functions-have-names.
Is functions-have-names still maintained?
The most recent release of functions-have-names (v1.2.3) was published 4 years ago.
Does functions-have-names run install scripts?
No. functions-have-names does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.