sternenseemann bd374243c0 npmHooks: use adjacent packages, not buildPackages ... Hooks are essentially implemented as special shell packages that run on their respective host platform. When they are used, they appear as nativeBuildInputs (as they need to be executed as part of the build of a package using them) so are taken from buildPackages relative to the derivation using them. Since the override in buildNpmPackage nullifies splicing, we take npmHooks from buildPackages manually. Fixes pkgsCross.ghcjs.buildPackages.emscripten and thus pkgsCross.ghcjs.haskellPackages.ghc.		2023-09-09 17:55:37 +02:00
..
default.nix	npmHooks: use adjacent packages, not buildPackages	2023-09-09 17:55:37 +02:00
npm-build-hook.sh	buildNpmPackage: add npmWorkspace and npmPruneFlags args	2023-06-29 07:42:25 -04:00
npm-config-hook.sh
npm-install-hook.sh	buildNpmPackage: use installManPage	2023-08-19 10:04:00 -07:00