-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
nodePackages: patch node2nix for npm v7+ and switch to building package set with current nodejs #193337
nodePackages: patch node2nix for npm v7+ and switch to building package set with current nodejs #193337
Conversation
The manual is failing build on master too so the CI failure seems unrelated to this change (fix for that is in #193338) |
@@ -9,16 +9,13 @@ let | |||
sourcePkg = fetchFromGitHub { | |||
owner = "pacien"; | |||
repo = "ldgallery"; | |||
rev = "v2.0"; | |||
sha256 = "1a82wy6ns1434gdba2l04crvr5waf03y02bappcxqci2cfb1cznz"; | |||
rev = "v2.1"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be derived from ldgallery-compiler.version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can be if you'd rather! I tried to make mostly minimal changes to get apps to build again after the update, so I left patterns like that as they were before. I'm happy to make the change though to avoid version desync for this particular package
CI build failure https://github.com/NixOS/nixpkgs/actions/runs/3144204430/jobs/5109902065 |
This fixes an issue with NPMv7+ / Node.js 16+
This package can still be used via `nodejs-14_x.pkgs.mdctl-cli`
…ge set with current nodejs
b60afbf
to
b3ec8d4
Compare
I've rebased the PR to pull in the manual fix from #193338 (unlucky timing I guess that I rebased initially in the 1 hour manual was broken) |
There will absolutely be some failures to fix, feel free to update if you find anything odd, happy to help. |
Thank you! I noticed some of the aarch64-linux and -darwin builds failed on ofborg (I don't have a Mac) so I was actually looking through those logs now to see if something broke that shouldn't have I will additionally watch Hydra for new failures in the next evaluation, in case I missed anything and can trace back any new failures to this PR |
Skimming one of those logs, it looks like it's just timeouts :) |
Follow-up to NixOS#193337 to fix several x86_64-darwin build failures due to missing xcrun/xcodebuild
I've fixed all of the Hydra regressions due to this PR from https://hydra.nixos.org/eval/1782541#tabs-now-fail in follow-up PR #193533 |
Follow-up to #193337 to fix several x86_64-darwin build failures due to missing xcrun/xcodebuild
I just noticed this PR. Great work! Thanks a lot for working on this! |
I realise I didn't say this properly, but I'm hugely grateful too. Before this lits of npm packages were simply broken because they deprecated the node 14 APIs. Thanks again ! |
I'm glad I could help! I know having nodePackages/node2nix not working with current Node.js versions was starting to get in my way a bunch for packaging stuff (even if I don't use Node much personally), so I implemented this update when I finally had the time and mental bandwidth to
I don't have a ko-fi or anything like that and I don't have a good way to accept money right now, but I do really appreciate the offer! ❤️ |
Description of changes
This PR updates the
nodePackages
set to the latest Node.js LTS of thenodejs
package, which is nownodejs-18_x
. It does this by importing the fix from svanderburg/node2nix#302 that implements compatbility with NPM v7+ / Node.js 16+Some notes:
nodePackages
did not regress after this update. Only one package does not build in this PR that built before,nodePackages.mdctl-cli
, since it does not support Node.js >14 yet, so I have marked it broken (but it still can be used vianodejs-14_x.pkgs.mdctl-cli
as needed)npm rebuild
step before, and while I'm not sure if they were still somehow working properly (I didn't test), I updated their build inputs to allow them to build with newer Node.jsNote: I did not target this towards staging since the rebuild count is not too big, but if it should be targeted towards staging to help breakages get caught there first, I'm happy to retarget this branch
Closes #132456, closes #145432, closes #146440, closes #170722, closes #187337
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes