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

./pkgs/development/node-packages/generate.sh never ends #232411

Closed
yajo opened this issue May 17, 2023 · 7 comments
Closed

./pkgs/development/node-packages/generate.sh never ends #232411

yajo opened this issue May 17, 2023 · 7 comments
Labels

Comments

@yajo
Copy link
Contributor

yajo commented May 17, 2023

Describe the bug

Well, it actually ends at some point, but after an extreme amount of hours.

Now, #221164 has conflicts and I just can't find the time to update the PR (not because I don't have time, but because the script always takes longer than my work schedule).

Steps To Reproduce

Steps to reproduce the behavior:

  1. Add "@prettier/plugin-xml" to node-packages.json
  2. Run ./pkgs/development/node-packages/generate.sh

Expected behavior

That file only has about 400 packages. It shouldn't take so many hours to complete!

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

Notify maintainers

Metadata

Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
this path will be fetched (0.00 MiB download, 0.00 MiB unpacked):
  /nix/store/8pfc9wfmn73bfz4ha0wmxvggk2wy9mpk-nix-info
copying path '/nix/store/8pfc9wfmn73bfz4ha0wmxvggk2wy9mpk-nix-info' from 'ssh://eu.nixbuild.net'...
 - system: `"x86_64-linux"`
 - host os: `Linux 6.2.15-300.fc38.x86_64, Fedora Linux, 38.20230515.0 (Silverblue), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(yajo): `"nixpkgs"`
 - nixpkgs: `/var/home/yajo/.nix-defexpr/channels/nixpkgs`
@yajo yajo added the 0.kind: bug Something is broken label May 17, 2023
@figsoda
Copy link
Member

figsoda commented May 17, 2023

cc @NixOS/node

@winterqt
Copy link
Member

winterqt commented May 17, 2023

We're not really too interested in solving this at the moment, moreso reducing the size of the set.

Feel free to try to fix it in node2nix, though! Would be a great improvement.

@lilyinstarlight
Copy link
Member

To clarify, new packages should be using buildNpmPackage (or similar) instead of using the older node2nix-based method, if those packages are supported by buildNpmPackage (e.g. see #229475)

We don't really have enough bandwidth ourselves to maintain node2nix and it has a lot of rather problematic issues (the massive size of the nodePackages set, which must fetch the metadata and files of ~10k packages, included -- but also it does a lot of things wrong and is based on a rather old model of how npm works)

@NotAShelf
Copy link
Member

Speaking of npm, would there be any chance we see the pnpm toolkit introduced to nix build procedure, perhaps somethinig like buildPnpmPackage? I vaguely recall seeing an issue/discussion on it, but couldn't find it with a quick search.

@lilyinstarlight
Copy link
Member

Speaking of npm, would there be any chance we see the pnpm toolkit introduced to nix build procedure, perhaps somethinig like buildPnpmPackage? I vaguely recall seeing an issue/discussion on it, but couldn't find it with a quick search.

It's on the roadmap, but not a current focus (the npm tooling is still busted enough as-is...)

We're gonna start tracking that in #231513

@yajo
Copy link
Contributor Author

yajo commented May 18, 2023

I guess this is a duplicate of #229475 then. Thanks everyone, I'll follow your suggestions 😊

I guess the very immediate action to take would be to change the docs, because I actually came to this problem following https://nixos.org/manual/nixpkgs/stable/#id-1.5.8.21.6.10

@yajo yajo closed this as not planned Won't fix, can't repro, duplicate, stale May 18, 2023
@lilyinstarlight
Copy link
Member

I guess the very immediate action to take would be to change the docs, because I actually came to this problem following

Yeah the docs do need updating there for sure. I guess I should probably try to sneak a docs update in soon so it makes it into the stable release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants