Skip to content

esm: unflag import.meta.resolve #49028

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nodejs-github-bot merged 8 commits into from
Aug 13, 2023
Merged

esm: unflag import.meta.resolve #49028

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
7797444
esm: unflag import.meta.resolve
guybedford Aug 5, 2023
719c418
update pr url
guybedford Aug 5, 2023
1c5c2d8
replaceme
guybedford Aug 5, 2023
f865a1d
docs changes
guybedford Aug 5, 2023
69796fd
pr feedback
guybedford Aug 6, 2023
09f2bef
Update lib/internal/modules/esm/initialize_import_meta.js
guybedford Aug 7, 2023
c94c64e
fixup default arg
guybedford Aug 7, 2023
a0ab43d
add stability, fix typos
GeoffreyBooth Aug 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
add stability, fix typos
  • Loading branch information
@GeoffreyBooth
GeoffreyBooth committed Aug 13, 2023
commit a0ab43dbcbf6983580ad1e0e37b1ca2a9592a615
11 changes: 7 additions & 4 deletions doc/api/esm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -344,7 +344,10 @@ changes:
flagged.
-->

* `specifier` {string} The module specifier to resolve relative to `parent`.
> Stability: 1.2 - Release candidate

* `specifier` {string} The module specifier to resolve relative to the
current module.
* Returns: {string} The absolute (`file:`) URL string for the resolved module.

[`import.meta.resolve`][] is a module-relative resolution function scoped to
Expand All @@ -366,10 +369,10 @@ import.meta.resolve('./dep', import.meta.url);
> **Caveat** This can result in synchronous file-system operations, which
> can impact performance similarly to `require.resolve`.

Previously, Node.js implemented an asynchonous resolver which also permitted
Previously, Node.js implemented an asynchronous resolver which also permitted
a second contextual argument. The implementation has since been updated to be
synchronous, with the second contextual `parent` URL still accessible behind the
`--experimental-import-meta-resolve` flag:
synchronous, with the second contextual `parent` argument still accessible
behind the `--experimental-import-meta-resolve` flag:

* `parent` {string|URL} An optional absolute parent module URL to resolve from.

Expand Down