Skip to content

Conversation

@JakobJingleheimer
Copy link
Member

Reverts #43363

Per nodejs/loaders#90

@nodejs/releasers @danielleadams We decided to revert the PR which was previously marked as blocking several other PRs; those other PRs remain unblocked. Apologies for the confusion.

@JakobJingleheimerJakobJingleheimer added esm Issues and PRs related to the ECMAScript Modules implementation. loaders Issues and PRs related to ES module loaders labels Jun 21, 2022
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/modules

@nodejs-github-botnodejs-github-bot added the needs-ci PRs that need a full CI run. label Jun 21, 2022
@GeoffreyBooth
Copy link
Member

GeoffreyBooth commented Jun 21, 2022

Request fast track. @nodejs/loaders

@GeoffreyBoothGeoffreyBooth added the fast-track PRs that do not need to wait for 48 hours to land. label Jun 21, 2022
@github-actions
Copy link
Contributor

Fast-track has been requested by @GeoffreyBooth. Please 👍 to approve.

Copy link
Contributor

@guybedfordguybedford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed in the loaders meeting, this takes the pressure off the design space for now, and hopefully with some progress on threaded loaders, syncification of the resolver can become possible that way. And this PR can always be added back if it comes to that.

Copy link
Contributor

@aduh95aduh95 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RSLGTM

@nodejs-github-bot

This comment was marked as outdated.

@GeoffreyBooth
Copy link
Member

cc @juanarbol, please make sure that this revert is processed before the next release (in other words, let’s make sure that #43363 gets reverted and therefore doesn’t go out in the next release).

nodejs/Release#737

@richardlau
Copy link
Member

cc @juanarbol, please make sure that this revert is processed before the next release (in other words, let’s make sure that #43363 gets reverted and therefore doesn’t go out in the next release).

nodejs/Release#737

If #43363 hasn't gone out in a release we can mark it with dont-land-on-* labels.

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@JakobJingleheimerJakobJingleheimer added the commit-queue Add this label to land a pull request using GitHub Actions. label Jun 22, 2022
@nodejs-github-botnodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Jun 22, 2022
@nodejs-github-botnodejs-github-bot merged commit 3c04034 into mainJun 22, 2022
@nodejs-github-bot
Copy link
Collaborator

Landed in 3c04034

@aduh95aduh95 deleted the revert-43363-esm/synchronous-resolve-hook branch June 22, 2022 07:15
@GeoffreyBooth
Copy link
Member

@richardlau This is the revert; we want it to land in any branch where the original PR landed . . . ?

@richardlau
Copy link
Member

@GeoffreyBooth AFAIK #43363 hasn't landed on any of the staging branches.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

esmIssues and PRs related to the ECMAScript Modules implementation.fast-trackPRs that do not need to wait for 48 hours to land.loadersIssues and PRs related to ES module loadersneeds-ciPRs that need a full CI run.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

@JakobJingleheimer@nodejs-github-bot@GeoffreyBooth@richardlau@guybedford@aduh95@VoltrexKeyva