-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENOTCACHED / Dependency not found in cache #106
Comments
I also ran into this (using a git redirect in pkg json) and can confirm that downgrading to node@6 helps but it is unfortunate. @demaisj: did you maybe come across another workaround since posting this? (Apart from publishing a package to a registry maybe) |
ps: this also uses scuttle-shell, which depends on systrayhelper NixOS/nixpkgs#45997 hit a bug using node2nix -8 which is why i'm trying 6 right now: svanderburg/node2nix#106 (comment)
ps: this also uses scuttle-shell, which depends on systrayhelper NixOS/nixpkgs#45997 hit a bug using node2nix -8 which is why i'm trying 6 right now: svanderburg/node2nix#106 (comment)
ps: this also uses scuttle-shell, which depends on systrayhelper NixOS/nixpkgs#45997 hit a bug using node2nix -8 which is why i'm trying 6 right now: svanderburg/node2nix#106 (comment)
Any progress here? I get a similar error having
|
I think I have found the problem -- apparently some tarballs in the NPM registry bundle a When you run I now modified You can try it by installing the development version, by cloning the Git repo and running: $ nix-env -f default.nix -iA package |
I tried again with the new version but I still get Here is the |
node2ix 1.7.0 now contains a workaround for NPM dependencies in the registry that have package-lock.json files. This release should be able to deply this. |
I just started having this issue. node2nix 1.8.0, trying to build @bigcommerce/stencil-cli. When I checkout that repo and run node2nix with the lock file, it worked, but when I tried to just use a node-packages.json listing the one package, it stopped being able to build. |
I'm getting this error in 1.9.0 https://gist.github.com/dustinlacewell/b1b45edd7bec6abbaa4d833da0c298aa |
These days, support for npm's package-lock.json seems to besser than for yarn, so let's drop yarn2nix which is not quite where it needs to be yet (we pinned an experimental branch after all) and use napalm instead. For this we have to migrate from yarn to npm completely. Using npmlock2nix would be preferrable (as it doesn't require building a Haskell registry server), but there we end up running into an unsolved issue [1]. [1]: svanderburg/node2nix#106
These days, support for npm's package-lock.json seems to besser than for yarn, so let's drop yarn2nix which is not quite where it needs to be yet (we pinned an experimental branch after all) and use napalm instead. For this we have to migrate from yarn to npm completely. Using npmlock2nix would be preferrable (as it doesn't require building a Haskell registry server), but there we end up running into an unsolved issue [1]. [1]: svanderburg/node2nix#106
Hmm. I'm getting this as well with 1.9.0, trying to package cli-highlight to install in my Nixos system. To generate the nix files I'm just running: nix run 'nixpkgs#nodePackages.node2nix' -- -i node-packages.json (where node-packages.json just contains Interestingly the resulting nix files build fine if I {
description = "Basic flake packaging of cli-highlight node app";
outputs = { self, nixpkgs }:
let system = "x86_64-linux";
pkgs = nixpkgs.legacyPackages.x86_64-linux;
called = pkgs.callPackage ./default.nix { inherit pkgs system; };
in {
packages.${system}.cli-highlight = called.cli-highlight;
defaultPackage.${system} = self.packages.${system}.cli-highlight;
};
} (Or call it from my Nixos system flake, which is what I really want to do) |
I'm using node2nix 1.11.1, from commit 68f5735. I added a simple > node2nix -i node-packages.json -16 --include-peer-dependencies
The resulting directory is: prettier.zip (there you can see the Just uncompress, > nix-build -A '@prettier/plugin-xml'
|
Hello,
I'm having trouble building multiple packages from github repositories. Upon the
npm install
step, npm reports that a dependency is missing from cache, despite it being built earlier.To simplify steps to reproduce, here's the
node-packages.json
file narrowed down to the package that fails to build:I use the
node2nix --nodejs-8 --input node-packages.json
command to generate the derivations.Upon build, npm reports that the
ms
dependency is missing:I have no idea what could cause this, all required versions of ms are downloaded & built prior to executing npm install.
I can not bypass the npm install step, as I need it to create the executable files of the packages.
Note: this error doesn't occur when building for nodejs-6_x
The text was updated successfully, but these errors were encountered: