Skip to content
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.

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

module: simplify findPackageJSON implementation #55543

Merged
merged 1 commit into from
Nov 2, 2024

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented Oct 25, 2024

@aduh95 aduh95 added the request-ci Add this label to start a Jenkins CI on a PR. label Oct 25, 2024
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/loaders

@nodejs-github-bot nodejs-github-bot added module Issues and PRs related to the module subsystem. needs-ci PRs that need a full CI run. labels Oct 25, 2024
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Oct 25, 2024
@nodejs-github-bot
Copy link
Collaborator

Copy link

codecov bot commented Oct 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.32%. Comparing base (e312d60) to head (b2e04e2).
Report is 213 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #55543      +/-   ##
==========================================
- Coverage   88.43%   88.32%   -0.12%     
==========================================
  Files         654      654              
  Lines      187657   187629      -28     
  Branches    36117    36041      -76     
==========================================
- Hits       165951   165718     -233     
- Misses      14947    15137     +190     
- Partials     6759     6774      +15     
Files with missing lines Coverage Δ
lib/internal/modules/package_json_reader.js 99.38% <100.00%> (-0.02%) ⬇️

... and 33 files with indirect coverage changes

Copy link
Member

@JakobJingleheimer JakobJingleheimer left a comment

Choose a reason for hiding this comment

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

Thanks! I was gonna do whilst my friend was getting ready this morning ;)

Could you also restore #55412 (review)

I dunno how it got removed.

@aduh95 aduh95 added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Oct 26, 2024
@aduh95
Copy link
Contributor Author

aduh95 commented Oct 26, 2024

Could you also restore #55412 (review)

#55549

@marco-ippolito marco-ippolito added the commit-queue Add this label to land a pull request using GitHub Actions. label Nov 2, 2024
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Nov 2, 2024
@nodejs-github-bot nodejs-github-bot merged commit c0db893 into nodejs:main Nov 2, 2024
72 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in c0db893

@aduh95 aduh95 deleted the simplify-find-pjson branch November 2, 2024 16:33
louwers pushed a commit to louwers/node that referenced this pull request Nov 2, 2024
PR-URL: nodejs#55543
Reviewed-By: Jacob Smith <jacob@frende.me>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
aduh95 added a commit that referenced this pull request Nov 5, 2024
PR-URL: #55543
Reviewed-By: Jacob Smith <jacob@frende.me>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
tpoisseau pushed a commit to tpoisseau/node that referenced this pull request Nov 21, 2024
PR-URL: nodejs#55543
Reviewed-By: Jacob Smith <jacob@frende.me>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
@ruyadorno
Copy link
Member

This commit does not land cleanly on v22.x-staging and will need manual backport in case we want it in v22.x.

@ruyadorno ruyadorno added the backport-requested-v22.x PRs awaiting manual backport to the v22.x-staging branch. label Nov 27, 2024
@JakobJingleheimer
Copy link
Member

JakobJingleheimer commented Nov 29, 2024

How do I find the commit hash I should use to create the backport? Is it the one in main?

Also, can I combine this backport with the one for #55412, since this is directly dependent/related to that?

@aduh95
Copy link
Contributor Author

aduh95 commented Nov 29, 2024

You can use the one given on #55543 (comment), or the one that landed on v23.x. It should definitely be combined yes

JakobJingleheimer pushed a commit to JakobJingleheimer/node that referenced this pull request Nov 29, 2024
PR-URL: nodejs#55543
Reviewed-By: Jacob Smith <jacob@frende.me>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
aduh95 added a commit to JakobJingleheimer/node that referenced this pull request Dec 10, 2024
PR-URL: nodejs#55543
Backport-PR-URL: nodejs#56074
Reviewed-By: Jacob Smith <jacob@frende.me>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
PR-URL: nodejs#55412
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. backport-requested-v22.x PRs awaiting manual backport to the v22.x-staging branch. module Issues and PRs related to the module subsystem. needs-ci PRs that need a full CI run.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants