nodePackages{,_latest}: remove and throw

### buildNpmPackage {#javascript-buildNpmPackage}

`buildNpmPackage` allows you to package npm-based projects in Nixpkgs without the use of an auto-generated dependencies file (as used in [node2nix](#javascript-node2nix)).

`buildNpmPackage` allows you to package npm-based projects in Nixpkgs without the use of an auto-generated dependencies file.

It works by utilizing npm's cache functionality -- creating a reproducible cache that contains the dependencies of a project, and pointing npm to it.

Here's an example:

This package puts the corepack wrappers for pnpm and yarn in your PATH, and they will honor the `packageManager` setting in the `package.json`.

### node2nix {#javascript-node2nix}

#### Preparation {#javascript-node2nix-preparation}

You will need to generate a Nix expression for the dependencies. Don't forget the `-l package-lock.json` if there is a lock file. Most probably you will need the `--development` to include the `devDependencies`

So the command will most likely be:

```sh

node2nix --development -l package-lock.json

```

See `node2nix` [docs](https://github.com/svanderburg/node2nix) for more info.

#### Pitfalls {#javascript-node2nix-pitfalls}

- If upstream package.json does not have a "version" attribute, `node2nix` will crash. You will need to add it like shown in [the package.json section](#javascript-upstream-package-json).

- `node2nix` has some [bugs](https://github.com/svanderburg/node2nix/issues/238) related to working with lock files from npm distributed with `nodejs_16`.

- `node2nix` does not like missing packages from npm. If you see something like `Cannot resolve version: vue-loader-v16@undefined` then you might want to try another tool. The package might have been pulled off of npm.

### pnpm {#javascript-pnpm}

pnpm is available as the top-level package `pnpm`. Additionally, there are variants pinned to certain major versions, like `pnpm_8`, `pnpm_9` and `pnpm_10`, which support different sets of lock file versions.

    "index.html#katamari-tarballs",

    "index.html#individual-tarballs",

    "index.html#generating-nix-expressions",

    "index.html#overriding-the-generator"

    "index.html#overriding-the-generator",

    "index.html#javascript-node2nix",

    "index.html#javascript-node2nix-preparation",

    "index.html#javascript-node2nix-pitfalls"

  ],

  "sec-nixpkgs-release-26.05-lib": [

    "release-notes.html#sec-nixpkgs-release-26.05-lib"

  "javascript-corepack": [

    "index.html#javascript-corepack"

  ],

  "javascript-node2nix": [

    "index.html#javascript-node2nix"

  ],

  "javascript-node2nix-preparation": [

    "index.html#javascript-node2nix-preparation"

  ],

  "javascript-node2nix-pitfalls": [

    "index.html#javascript-node2nix-pitfalls"

  ],

  "javascript-pnpm": [

    "index.html#javascript-pnpm"

  ],

<!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. -->

- The `nodePackages` package set has been removed entirely from nixpkgs. This package set was created to ease the maintenance burden of maintaining lots of

  NodeJS-based packages within nixpkgs, but became a burden itself. Over the past several releases, there has been a focus on removing it in favor of the more modern nixpkgs packaging strategies.

  After a long time, this package set has been deprecated and removed. If you are using its package set in your own config, please use the top-level packages instead.(i.e `pkgs.package-name` instead of `pkgs.nodePackages.package-name`).

- Note that the above `nodePackages` removal also coincides with the removal of `node2nix` and its tooling, which have been deprecated for a long time.

- `xfce.mkXfceDerivation` has been deprecated (i.e. conditioned behind `nixpkgs.config.allowAliases`)

  and will be removed in NixOS 26.11, please use `stdenv.mkDerivation` directly. You can migrate by

  adding `pkg-config`, `xfce4-dev-tools`, and `wrapGAppsHook3` to your `nativeBuildInputs` and

> [!IMPORTANT]

> There is currently an active project to [remove packages from `nodePackages`](https://github.com/NixOS/nixpkgs/issues/229475).

> Please consider adding new packages using [another method](https://nixos.org/manual/nixpkgs/unstable/#javascript-tool-specific).

This folder contains a generated collection of [npm packages](https://npmjs.com/) that can be installed with the Nix package manager.

As a rule of thumb, the package set should only provide _end-user_ software packages, such as command-line utilities.

Libraries should only be added to the package set if there is a non-npm package that requires it.

When it is desired to use npm libraries in a development project, use the `node2nix` generator directly on the `package.json` configuration file of the project.

The package set provides support for the official stable Node.js versions.

The latest stable LTS release in `nodePackages`, as well as the latest stable current release in `nodePackages_latest`.

If your package uses native addons, you need to examine what kind of native build system it uses. Here are some examples:

- `node-gyp`

- `node-gyp-builder`

- `node-pre-gyp`

After you have identified the correct system, you need to override your package expression while adding the build system as a build input.

For example, `dat` requires `node-gyp-build`, so we override its expression in [pkgs/development/node-packages/overrides.nix](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/node-packages/overrides.nix):

```nix

{

  dat = prev.dat.override (oldAttrs: {

    buildInputs = [

      final.node-gyp-build

      pkgs.libtool

      pkgs.autoconf

      pkgs.automake

    ];

    meta = oldAttrs.meta // {

      broken = since "12";

    };

  });

}

```

### Adding and updating JavaScript packages in Nixpkgs

To add a package from npm to Nixpkgs:

1. Modify [pkgs/development/node-packages/node-packages.json](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/node-packages/node-packages.json) to add, update or remove package entries to have it included in `nodePackages` and `nodePackages_latest`.

2. Run the script:

   ```sh

   ./pkgs/development/node-packages/generate.sh

   ```

3. Build your new package to test your changes:

   ```sh

   nix-build -A nodePackages.<new-or-updated-package>

   ```

    To build against the latest stable current Node.js version (e.g. 18.x):

    ```sh

    nix-build -A nodePackages_latest.<new-or-updated-package>

    ```

    If the package doesn't build, you may need to add an override as explained above.

4. Add and commit all modified and generated files.

For more information about the generation process, consult the [README.md](https://github.com/svanderburg/node2nix) file of the `node2nix` tool.

To update npm packages in Nixpkgs, run the same `generate.sh` script:

```sh

./pkgs/development/node-packages/generate.sh

```

#### Git protocol error

Some packages may have Git dependencies from GitHub specified with `git://`.

GitHub has [disabled unencrypted Git connections](https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git), so you may see the following error when running the generate script:

```

The unauthenticated git protocol on port 9418 is no longer supported

```

Use the following Git configuration to resolve the issue:

```sh

git config --global url."https://github.com/".insteadOf git://github.com/

```