| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This would cause any drv to be rebuilt when any part of the default.nix changes.
What we actually care about is the two JS files though, so simply reference them
directly.
Co-authored-by: Infinidoge <infinidoge@inx.moe>
|
|
|
|
|
|
|
|
To reduce dependencies (mainly nix-prefetch-git and through that git,
git-lfs) when we just need to fixup a lock file, eg when building electron.
This also tries to avoid needless rebuilds when eg. golang is updated.
Also this cleans up and combined the build/installPhase of both tools to
be a lot simpler.
|
|
The nixpkgs-unstable channel's programs.sqlite was used to identify
packages producing exactly one binary, and these automatically added
to their package definitions wherever possible.
|
|
This assumes that downstream users of `buildNpmPackage` would rather our
own built `node_modules` be copied to the output rather than only the
`bundleDependencies` specified in the `package.json` file.
Having the latter behavior seems unexpected and unintuitive, and would
not work as installing from an `npm pack` is intended to (since doing
that would not do a `rebuild` step on those dependencies and it would
skip reifying a full dependency tree).
|
|
This is an alternative to `fetchNpmDeps` that is notably different in that it uses metadata from `package.json` & `package-lock.json` instead of specifying a fixed-output hash.
Notable features:
- IFD free.
- Only fetches a node dependency once. No massive FODs.
- Support for URL, Git and path dependencies.
- Uses most of the existing `npmHooks`
`importNpmLock` can be used _only_ in the cases where we need to check in a `package-lock.json` in the tree.
Currently this means that we have 13 packages that would be candidates to use this function, though I expect most usage to be in private repositories.
This is upstreaming the builder portion of https://github.com/adisbladis/buildNodeModules into nixpkgs (different naming but the code is the same).
I will archive this repository and consider nixpkgs the new upstream once it's been merged.
For more explanations and rationale see https://discourse.nixos.org/t/buildnodemodules-the-dumbest-node-to-nix-packaging-tool-yet/35733
Example usage:
``` nix
stdenv.mkDerivation {
pname = "my-nodejs-app";
version = "0.1.0";
src = ./.;
nativeBuildInputs = [
importNpmLock.hooks.npmConfigHook
nodejs
nodejs.passthru.python # for node-gyp
npmHooks.npmBuildHook
npmHooks.npmInstallHook
];
npmDeps = buildNodeModules.fetchNodeModules {
npmRoot = ./.;
};
}
```
|
|
in package.json
|
|
for entire hook
|
|
prefetch-npm-deps: add support for npm alias schema in version spec
|
|
lilyinstarlight/fix/prefetch-npm-deps-more-bad-lockfiles
|
|
|
|
prefetch-yarn-deps: Fix handling of scoped packages
|
|
|
|
|
|
|
|
|
|
|
|
element-{web,desktop}: 1.11.47 -> 1.11.50
|
|
lilyinstarlight/fix/prefetch-npm-deps-error-when-no-cached-deps
|
|
Found while updating element-web
|
|
|
|
|
|
|
|
... and simplify `prefetchYarnDeps`
|
|
|
|
Ideally fetch-yarn-deps could do like some other fetchers and support
using SSL_CERT_FILE if it exists and also only verify integrity on FOD
hash unless using an empty/test hash.
But this should keep at least the same semantics as before the recent
Node.js change to stop using the built-in certificate store in favor of
the system one (which does not exist by default in the build sandbox).
|
|
|
|
lilyinstarlight/fix/yay-more-fixup-yarn-lock-stuff
prefetch-yarn-deps: re-add git hash for fixup
|
|
|
|
|
|
npmHooks.npmInstallHook: avoid script output in npm pack command
|
|
* buildNpmPackage: allow nodejs to be passed as argument
* Update doc/languages-frameworks/javascript.section.md
Co-authored-by: Lily Foster <lily@lily.flowers>
---------
Co-authored-by: Lily Foster <lily@lily.flowers>
|
|
lilyinstarlight/fix/prefetch-npm-deps-network-error-recovery
prefetch-npm-deps: read url bodies within the retry loop
|
|
|
|
|
|
buildNpmPackage: support makeWrapperArgs
|
|
build-npm-package: give a hint when npm prune fails
|
|
Co-authored-by: Lily Foster <lily@lily.flowers>
|
|
|
|
instead of rejecting, given that the expected hash may not be known/provided.
|
|
|
|
prefetch-npm-deps: add support for NIX_NPM_TOKENS env var
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
