</>PackageGraphPackageGraph

create-require

npmv1.1.1TypeScript

Polyfill for Node.js module.createRequire (<= v12.2.0)

Not recommended for new projects

No — create-require should not be adopted for new projects. Last published 2113 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 2113 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 6.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 create-require to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

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

6.1 KB
Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the create-require README.

function createRequire (filename: string | URL): NodeRequire;

Dependencies

Declared by create-require v1.1.1. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (4)

@nuxtjs/eslint-config latesteslint lateststandard-version latesttap latest

Used by

Popular packages that depend on create-require.

Relationship graph

Dependencies (left) and dependents (right) of create-require.

ts-nodecreate-require
create-require dependencies dependents

Frequently installed together

Release history

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

Recent versions of create-require
VersionPublishedSizeLicense
1.1.1latest5 years ago6.1 KBMIT
1.1.05 years ago5.8 KBMIT
1.0.26 years ago5.4 KBMIT
1.0.16 years ago4.7 KBMIT
1.0.06 years ago4.5 KBMIT
0.0.16 years ago4.4 KBMIT
0.0.06 years ago73 BMIT

Overview

create-require is an npm package that polyfill for Node.js module.createRequire (<= v12.2.0). It has 1 known dependents in the graph. The latest version is 1.1.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need polyfill for Node.js module.createRequire (<= v12.2.0) 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 create-require?

No — create-require should not be adopted for new projects. Last published 2113 days ago.

How do I install create-require?

Run `npm install create-require` to add create-require to your npm project.

What license is create-require released under?

create-require is distributed under the MIT license.

How popular is create-require?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on create-require.

Is create-require still maintained?

The most recent release of create-require (v1.1.1) was published 5 years ago.

Does create-require run install scripts?

No. create-require does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.