also the error I get when the hash is wrong looks like this:

patching script interpreter paths in /nix/store/p2h78fcx52hwp92aj93p42zfgjf0q4ip-prisma-language-server-6.16.2-npm-deps
error: hash mismatch in fixed-output derivation '/nix/store/70y5ydbl5i3iil4zxl6dcgalr0wlx56r-prisma-language-server-6.16.2-npm-deps.drv':
         specified: sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
            got:    sha256-XouMkRE1QQvr7keIF7q1jkCE21/O9jyRfbmqm820yas=

as opposed to the ENOTCACHED error I was talking about above

this is what I have so far:

{
  lib,
  buildNpmPackage,
  fetchFromGitHub,
}:

buildNpmPackage (finalAttrs: {
  pname = "prisma-language-server";
  version = "6.16.2";

  src = fetchFromGitHub {
    owner = "prisma";
    repo = "language-tools";
    tag = "${finalAttrs.version}";
    hash = "sha256-UZP0pLcbMeaYI0ytOJ68l/ZEC9dBhohJZyTU99p+1QM=";
  };

  # npmPackFlags = [ "--ignore-scripts" ];

  # The original lockfile from the upstream source is broken,
  # so we need to use a rebuilt version of the package-lock file.
  postPatch = ''
    cp ${./package-lock.json} package-lock.json
  '';

  npmDepsHash = "sha256-XouMkRE1QQvr7keIF7q1jkCE21/O9jyRfbmqm820yas=";

  # NODE_OPTIONS = "--openssl-legacy-provider";

  meta = {
    description = "";
    homepage = "https://github.com/prisma/language-tools#readme";
    license = lib.licenses.asl20;
    maintainers = with lib.maintainers; [ mmkaram ];
  };
})

In reply to @tomodachi94:matrix.org
In case you missed it on GitHub: this is queued to be merged. It will start trickling into channels soon (https://nixpk.gs is helpful for tracking that progression)

In reply to @acidbong:envs.net
evening, fellers and felines
related to Albert's package: his current effort looks like this, and i'm trying to replace the NPM archive with the Github source and run npm run build in it (diff), but tsc fails with this kinda error: https://termbin.com/9t7d
what could be the culprit?

In reply to @acidbong:envs.net
evening, fellers and felines
related to Albert's package: his current effort looks like this, and i'm trying to replace the NPM archive with the Github source and run npm run build in it (diff), but tsc fails with this kinda error: https://termbin.com/9t7d
what could be the culprit?

It depends, ime building from upstream source is better as it is easier to debug issues from source inputs to compiled outputs.

Archives from npm often contain already compiled archives, which can be an easy way to sidestep a complex compile/build step.(similar to packaging upstream binaries).