</>PackageGraphPackageGraph

rechoir

npmv0.8.0

Prepare 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.

1
Direct dependencies

Runtime packages this one declares itself.

7
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

274 KB
Install size

Unpacked size of this package plus its entire runtime tree.

4
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

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.

PackageWeekly downloadsDependentsLicenseLast release
rechoirthis page01MIT5 years ago
mime136.4M6MIT1 day ago
mrmime37.2M3MIT1 day ago
esm6.2M5MIT1 day ago
resolve-from08MIT1 day ago
make-error01ISC1 day ago

Dependencies

Declared by rechoir v0.8.0. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (1)

Dev (5)

eslint ^7.21.0eslint-config-gulp ^5.0.1expect ^27.0.0mocha ^8.3.0nyc ^15.1.0

Used by

Popular packages that depend on rechoir.

Relationship graph

Dependencies (left) and dependents (right) of rechoir.

resolveknexrechoir
rechoir dependencies dependents

Frequently installed together

Release history

No releases in the last two years, typically about 38 days apart.

Recent versions of rechoir
VersionPublishedSizeLicense
0.8.0latest5 years ago8.4 KBMIT
0.7.15 years ago8.7 KBMIT
0.7.07 years ago7.7 KBMIT
0.6.211 years agoMIT
0.6.111 years agoMIT
0.6.011 years agoMIT
0.5.011 years agoMIT
0.4.011 years agoMIT
0.3.011 years agoMIT
0.2.211 years agoMIT
0.2.112 years agoMIT
0.2.012 years agoMIT
0.1.012 years agoMIT

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.

Maintainers

Keywords

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.