get-nonce
npmv1.0.1TypeScriptreturns nonce
Not recommended for new projects
No — get-nonce should not be adopted for new projects. Last published 2288 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 2288 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 5.1 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 get-nonce 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 >=6
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the get-nonce README.
__webpack_nonce__ = uuid(); // for exampleget-nonce 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 |
|---|---|---|---|---|
| get-noncethis page | 0 | 1 | MIT | 6 years ago |
| schema-utils | 116.4M | 2 | MIT | 2 hours ago |
| babel-preset-expo | 7.2M | 1 | MIT | 2 hours ago |
| loader-runner | 0 | 1 | MIT | 2 hours ago |
| minimizer-webpack-plugin | 0 | 1 | MIT | 2 hours ago |
| rolldown | 0 | 4 | MIT | 2 hours ago |
Dependencies
Declared by get-nonce v1.0.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (2)
Used by
Popular packages that depend on get-nonce.
Relationship graph
Dependencies (left) and dependents (right) of get-nonce.
Frequently installed together
Release history
No releases in the last two years.
| Version | Published | Size | License |
|---|---|---|---|
| 1.0.1latest | 6 years ago | 5.1 KB | MIT |
| 1.0.0 | 6 years ago | 4.6 KB | MIT |
Overview
get-nonce is an npm package that returns nonce. It has 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 returns nonce and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
- Lean dependency tree (2 direct dependencies).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Keywords
Frequently asked questions
Should I use get-nonce?
No — get-nonce should not be adopted for new projects. Last published 2288 days ago.
How do I install get-nonce?
Run `npm install get-nonce` to add get-nonce to your npm project.
What license is get-nonce released under?
get-nonce is distributed under the MIT license.
How popular is get-nonce?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on get-nonce.
Is get-nonce still maintained?
The most recent release of get-nonce (v1.0.1) was published 6 years ago.
Does get-nonce run install scripts?
No. get-nonce does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.