toidentifier
npmv1.0.1Convert a string of words to a JavaScript identifier
Not recommended for new projects
No — toidentifier should not be adopted for new projects. Last published 1760 days ago.
- AAdoption: grade A, Excellent.
106.6M downloads per week and 1 known dependents.
- FMaintenance: grade F, Failing.
Last published 1760 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 4.6 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 3 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 toidentifier 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
- node >=0.6
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the toidentifier README.
var toIdentifier = require('toidentifier')
console.log(toIdentifier('Bad Request'))
// => "BadRequest"Dependencies
Declared by toidentifier v1.0.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (9)
Used by
Popular packages that depend on toidentifier.
Relationship graph
Dependencies (left) and dependents (right) of toidentifier.
Frequently installed together
An AST-based pattern checker for JavaScript.
Deprecate all the things
A small polyfill for Object.setprototypeof
HTTP status utility
Browser-friendly inheritance fully compatible with standard node.js inherits()
Release history
No releases in the last two years, typically about 1224 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.0.1latest | 4 years ago | 4.6 KB | MIT |
| 1.0.0 | 8 years ago | 4.2 KB | MIT |
| 0.0.1 | 8 years ago | — | MIT |
Overview
toidentifier is an npm package that convert a string of words to a JavaScript identifier. It is extremely widely used, with about 106.6M downloads per week and 1 known dependents in the graph. The latest version is 1.0.1, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need convert a string of words to a JavaScript identifier and value a battle-tested, widely-adopted 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
- Large, well-established user base (106.6M weekly downloads).
- 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
Frequently asked questions
Should I use toidentifier?
No — toidentifier should not be adopted for new projects. Last published 1760 days ago.
How do I install toidentifier?
Run `npm install toidentifier` to add toidentifier to your npm project.
What license is toidentifier released under?
toidentifier is distributed under the MIT license.
How popular is toidentifier?
toidentifier has approximately 106,560,626 downloads per week and 1 known dependent packages.
Is toidentifier still maintained?
The most recent release of toidentifier (v1.0.1) was published 4 years ago.
Does toidentifier run install scripts?
No. toidentifier does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.