Skip to content

esm: set all module customization hooks as release candidate #49597

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
merged 1 commit into from
Sep 13, 2023
Merged

esm: set all module customization hooks as release candidate #49597

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions doc/api/module.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ isBuiltin('wss'); // false
added: v20.6.0
-->

> Stability: 1.1 - Active development
> Stability: 1.2 - Release candidate

* `specifier` {string} Customization hooks to be registered; this should be the
same string that would be passed to `import()`, except that if it is relative,
Expand Down Expand Up @@ -166,7 +166,7 @@ changes:
`globalPreload`; added `load` hook and `getGlobalPreload` hook.
-->

> Stability: 1.1 - Active development
> Stability: 1.2 - Release candidate

<!-- type=misc -->

Expand Down Expand Up @@ -385,7 +385,7 @@ asynchronous operations (like `console.log`) to complete.
added: v20.6.0
-->

> Stability: 1.1 - Active development
> Stability: 1.2 - Release candidate

* `data` {any} The data from `register(loader, import.meta.url, { data })`.

Expand Down