nodePackages.rtlcss: use buildNpmPackage

[Lord-Valen]

Description of changes

See #229475.
Maintainer needed.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.11 Release Notes (or backporting 23.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[mkg20001]

is there any reason why not to keep it in nodePackages?

[Lord-Valen]

is there any reason why not to keep it in nodePackages?

nodePackages is unmaintainable. A change for one package can and usually will cause merge conflicts for other PRs. It's massive size means autogeneration can take hours. See #229475.

[dotlambda]

Suggested change

	{ buildNpmPackage, fetchFromGitHub, lib, ... }:
	{ buildNpmPackage, fetchFromGitHub, lib }: