npmpackage.info

Gathering detailed insights and metrics for import-from-esm

Other packages similar to import-from-esm

desm

1.3.1

get the file directory from import.meta.url

remote-esm

0.0.29

Import ESM from a remote endpoint

esm-loader

0.1.0

A ESM Loader for NodeJS and Browsers Allows to import modules from any source is extendible via modules.

@design-systems/next-esm-css

4.15.4

This package enables using the `esm` output from the `ds build` command in a Next.js based project. Currently Next.js doesn't allow `node_modules` to import their own CSS so using components from a `ds` based project doesn't work. [See this issue](https:/

Gathering detailed insights and metrics for import-from-esm

import-from-esm - 2.0.0 | npmpackage.info

import-from-esm

Almost drop-in "import-from" replacement that supports loading both ESM & CJS modules

2.0.0

MIT

JavaScript

12.99 kB

61,922,025 8

Installations

npm install import-from-esm

Developer Guide

BETA

Typescript

Yes

Module System

ESM

Min. Node Version

>=18.20

Node Version

22.12.0

NPM Version

10.9.2 Pull Requests

Open

15

Total

142

Closed

13

Merged

114

Issues

Open

4

Total

14

Closed

10

Releases

v2.0.0

Updated on Dec 31, 2024

v1.3.4

Updated on Apr 15, 2024

v1.4.0-alpha.1

Updated on Jan 19, 2024

v1.3.3

Updated on Nov 19, 2023

v1.3.2

Updated on Nov 19, 2023

v1.3.1

Updated on Nov 16, 2023

View All 19 releases

Languages

JavaScript

TypeScript

JavaScript (98.68%)

TypeScript (1.32%)

Developer

sheerlox

Download Statistics

Total Downloads

61,922,025

Last Day

66,256

Last Week

1,386,759

Last Month

6,012,095

Last Year

49,709,733

GitHub Statistics

MIT License

2 Stars

340 Commits

3 Forks

2 Watchers

17 Branches

3 Contributors

Updated on Mar 03, 2025

Maintainers

View All 3 Contributors

Package Meta Information

Latest Version

2.0.0

Package Id

import-from-esm@2.0.0

Unpacked Size

12.99 kB

Size

4.97 kB

File Count

NPM Version

10.9.2

Node Version

22.12.0

Published on

Dec 31, 2024

Total Downloads

Cumulative downloads

Total Downloads

61,922,025

Last Day

-17%

66,256

Compared to previous day

Last Week

-9.9%

1,386,759

Compared to previous week

Last Month

5.6%

6,012,095

Compared to previous month

Last Year

307%

49,709,733

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

debug import-meta-resolve

Dev Dependencies

@fast-check/ava @insurgent/export-map-test @insurgent/json-index-test @insurgent/json-main-test @insurgent/subpaths-test @insurgent/conventional-changelog-preset @semantic-release/changelog @semantic-release/git @types/debug ava c8 knip semantic-release tsd xo

import-from-esm

Overview

Import a module like with require() but from a given path (for ESM)

This library intends to be an almost drop-in replacement of import-from (from which it is forked), exposing the same API and behavior but also supporting ES modules (ESM). Just add await before importFrom/importFrom.silent

Motivation

The main benefit of using import-from is that it abstracts the need to resolve the path and create a require statement. Its code is really straightforward:

1(fromDirectory, moduleId) => createRequire(path.resolve(fromDirectory, "noop.js"))(moduleId);

In the case of import-from-esm, there are a few additional benefits because of the way ESM works:

Importing a package installed along a library (in the parent application) from that library is no longer possible (which was the issue that made me work on this library). You need to use import.meta.resolve, which is behind an experimental flag (although there's a ponyfill available at wooorm/import-meta-resolve, which import-from-esm uses under-the-hood).
If the file you're trying to import (whether relative, package, export map, etc ...) is a JSON file, you need to detect that and use import assertions or require (while the former is still in experimental).
File extensions are now mandatory for relative paths. import-from-esm re-introduces require's file extension discovery.

As you can see, there is quite a bit of complexity that is abstracted behind import-from-esm. The first bullet point issue affected both @semantic-release/commit-analyzer and @semantic-release/release-notes-generator. After spending hours on research to solve the issue, I realized that the work I was doing would benefit others as well, so I decided to create a package out of it.

As a proponent of ESM, I have put a lot of thought into poly-filling require features for import, but finally came to the conclusion that developing a package to facilitate the ecosystem transition to ESM by reducing friction was a good thing.

Install

$ npm install import-from-esm

Usage

1import importFrom from "import-from-esm";
2
3// there is a file at `./foo/bar.{js,mjs,cjs,json}`
4
5await importFrom("foo", "./bar");

API

importFrom(fromDirectory, moduleId)

Like require(), throws when the module can't be found.

importFrom.silent(fromDirectory, moduleId)

Returns undefined instead of throwing when the module can't be found.

fromDirectory

Type: string

Directory to import from.

moduleId

Type: string

What you would use in require().

Tip

Create a partial using a bound function if you want to import from the same fromDir multiple times:

1const importFromFoo = importFrom.bind(null, "foo");
2
3importFromFoo("./bar");
4importFromFoo("./baz");

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

10

Dependency-Update-Tool

Determines if the project uses a dependency update tool.

10

Security-Policy

Determines if the project has published a security policy.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

10

SAST

Determines if the project uses static code analysis.

10

License

Determines if the project has defined a license.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

10

Fuzzing

Determines if the project uses fuzzing.

10

CI-Tests

Determines if the project runs tests before pull requests are merged.

10

Contributors

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

8

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

8

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

2

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

1

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

Score

8

/10

Last Scanned on 2025-05-26T23:20:44Z

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More