ret
npmv0.5.0TypeScriptTokenizes a string that represents a regular expression.
Not recommended for new projects
No — ret should not be adopted for new projects. Last published 1273 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1273 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 68 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 ret 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 >=10
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the ret README.
const ret = require('ret');
let tokens = ret(/foo|bar/.source);ret 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 |
|---|---|---|---|---|
| retthis page | 0 | 1 | MIT | 3 years ago |
| is-regex | 75.1M | 1 | MIT | 1 day ago |
| regexp.prototype.flags | 0 | 1 | MIT | 1 day ago |
| escape-string-regexp | 316.5M | 8 | MIT | 1 day ago |
| css-tree | 0 | 5 | MIT | 1 day ago |
| anymatch | 0 | 1 | ISC | 1 day ago |
Dependencies
Declared by ret v0.5.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (7)
Used by
Popular packages that depend on ret.
Relationship graph
Dependencies (left) and dependents (right) of ret.
Frequently installed together
Release history
No releases in the last two years, typically about 114 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 0.5.0latest | 3 years ago | 68 KB | MIT |
| 0.4.3 | 3 years ago | 65 KB | MIT |
| 0.4.2 | 4 years ago | 64 KB | MIT |
| 0.4.1 | 4 years ago | 64 KB | MIT |
| 0.4.0 | 5 years ago | 60 KB | MIT |
| 0.3.2 | 5 years ago | 44 KB | MIT |
| 0.3.1 | 7 years ago | 23 KB | MIT |
| 0.3.0 | 7 years ago | 22 KB | MIT |
| 0.2.2 | 8 years ago | 17 KB | MIT |
| 0.2.1 | 8 years ago | — | MIT |
| 0.2.0 | 8 years ago | — | MIT |
| 0.1.15 | 9 years ago | — | MIT |
| 0.1.14 | 9 years ago | — | MIT |
| 0.1.13 | 9 years ago | — | MIT |
| 0.1.12 | 10 years ago | — | MIT |
Overview
ret is an npm package that tokenizes a string that represents a regular expression. It has 1 known dependents in the graph. The latest version is 0.5.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need tokenizes a string that represents a regular expression 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).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use ret?
No — ret should not be adopted for new projects. Last published 1273 days ago.
How do I install ret?
Run `npm install ret` to add ret to your npm project.
What license is ret released under?
ret is distributed under the MIT license.
How popular is ret?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on ret.
Is ret still maintained?
The most recent release of ret (v0.5.0) was published 3 years ago.
Does ret run install scripts?
No. ret does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.