rechoir
npmv0.8.0Prepare a node environment to require files with different extensions.
Not recommended for new projects
No — rechoir should not be adopted for new projects. Last published 1874 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- FMaintenance: grade F, Failing.
Last published 1874 days ago.
- BWeight: grade B, Good.
Pulls in 7 transitive packages, about 274 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 rechoir 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.
Licenses in the dependency tree
Every license you inherit by installing rechoir, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >= 10.13.0
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the rechoir README.
const config = require('interpret').extensions;
const rechoir = require('rechoir');
rechoir.prepare(config, './test/fixtures/test.coffee');
rechoir.prepare(config, './test/fixtures/test.csv');
rechoir.prepare(config, './test/fixtures/test.toml');
console.log(require('./test/fixtures/test.coffee'));
console.log(require('./test/fixtures/test.csv'));
console.log(require('./test/fixtures/test.toml'));rechoir 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 |
|---|---|---|---|---|
| rechoirthis page | 0 | 1 | MIT | 5 years ago |
| resolve-from | 214.2M | 8 | MIT | 16 hours ago |
| mime | 136.4M | 6 | MIT | 14 hours ago |
| mrmime | 37.2M | 3 | MIT | 15 hours ago |
| esm | 6.2M | 5 | MIT | 19 hours ago |
| resolve | 0 | 2 | MIT | 14 hours ago |
Dependencies
Declared by rechoir v0.8.0. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (1)
Dev (5)
Used by
Popular packages that depend on rechoir.
Relationship graph
Dependencies (left) and dependents (right) of rechoir.
Frequently installed together
the complete solution for node.js command-line programs
Resolve the path of a module like `require.resolve()` but from a given path
Lodash modular utilities.
An AST-based pattern checker for JavaScript.
A tiny (183B to 210B) and fast utility to ascend parent directories
Prettier is an opinionated code formatter
[](https://github.com/mmkal/expect-type/actions/workflows/ci.yml)  [](ht
PostgreSQL client - pure javascript & libpq with the same API
TypeScript execution environment and REPL for node.js, with source map support
Functions for dealing with a PostgreSQL connection string
fast mysql driver. Implements core protocol, prepared statements, ssl and compression in native JS
Tomorrow's ECMAScript modules today!
Release history
No releases in the last two years, typically about 38 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 0.8.0latest | 5 years ago | 8.4 KB | MIT |
| 0.7.1 | 5 years ago | 8.7 KB | MIT |
| 0.7.0 | 7 years ago | 7.7 KB | MIT |
| 0.6.2 | 11 years ago | — | MIT |
| 0.6.1 | 11 years ago | — | MIT |
| 0.6.0 | 11 years ago | — | MIT |
| 0.5.0 | 11 years ago | — | MIT |
| 0.4.0 | 11 years ago | — | MIT |
| 0.3.0 | 11 years ago | — | MIT |
| 0.2.2 | 11 years ago | — | MIT |
| 0.2.1 | 12 years ago | — | MIT |
| 0.2.0 | 12 years ago | — | MIT |
| 0.1.0 | 12 years ago | — | MIT |
Overview
rechoir is an npm package that prepare a node environment to require files with different extensions. It has 1 known dependents in the graph. The latest version is 0.8.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need prepare a node environment to require files with different extensions 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.
Frequently asked questions
Should I use rechoir?
No — rechoir should not be adopted for new projects. Last published 1874 days ago.
How do I install rechoir?
Run `npm install rechoir` to add rechoir to your npm project.
How many dependencies does rechoir have?
rechoir declares 6 direct dependencies and pulls in 7 packages in total once its runtime tree is resolved totalling about 274 KB on disk.
What license is rechoir released under?
rechoir is distributed under the MIT license.
How popular is rechoir?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on rechoir.
Is rechoir still maintained?
The most recent release of rechoir (v0.8.0) was published 5 years ago.
Does rechoir run install scripts?
No. rechoir does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.