In reply to @szucsitg:matrix.org
Thanks for debugging. I was looking through the yarn2nix code, and I think I found a work around. Use the tag's source tar.gz from github

In reply to @szucsitg:matrix.org
Thanks for debugging. I was looking through the yarn2nix code, and I think I found a work around. Use the tag's source tar.gz from github

In reply to @janne.hess:helsinki-systems.de
Full reproducer with the original files: https://github.com/dasJ/broken-npm-test

In reply to @szucsitg:matrix.org
I managed to figure out how to build the project mkYarnPackage. I added all packagges as workspaceDependencies, and it displays correctly in the offline cache derivation under node-modules (symlinked from deps). However when I want to build the React frontend a few folders down, it cannot find our own packages, while the node_modules folder correctly symlinked in root to offlineCache.

Like this:

error: builder for '/nix/store/2wh00drgf8sxhx6k8z7sx9fsbw35jb4y-account-settings-modules-1.0.0.drv' failed with exit code 1
error: 1 dependencies of derivation '/nix/store/9xvqxvm2hr9dq1d487zww0zywmnaa007-account-settings-1.0.0.drv' failed to build
error (ignored): error: cannot unlink '/private/tmp/nix-build-accept-shared-modules-1.0.0.drv-6/yarn_home/Library/Caches/Yarn/v6/npm-core-js-3.31.0-4471dd33e366c79d8c0977ed2d940821719db344-integrity/node_modules/core-js/internals': Directory not empty
error (ignored): error: cannot unlink '/private/tmp/nix-build-web-client-modules-4.123.0.drv-0/yarn_home/Library/Caches/Yarn/v6/npm-core-js-pure-3.31.0-052fd9e82fbaaf86457f5db1fadcd06f15966ff2-integrity/node_modules/core-js-pure/modules': Directory not empty
error: 1 dependencies of derivation '/nix/store/6il46rk23vm78ly4n5fiv63dghb6mh7d-frontend.drv' failed to build

Lily Foster: could you help me with packaging my nodejs app? These are the requirements:

You will need the output directory, the project's package.json, and the production dependencies in node_modules to run the application. Production dependencies can be generated by copying the package.json and package-lock.json and then running npm ci --omit dev (you can skip this step if your app doesn't have any dependencies). You can then start your app with this command:

node build
Development dependencies will be bundled into your app using Rollup. To control whether a given package is bundled or externalised, place it in devDependencies or dependencies respectively in your package.json.

This is what I have:

buildInputs = with pkgs; [
        nodejs_20
      ];
      src = ./.;
      npmDepsHash = "sha256-mTpjBKTIJkYVj2jrH5lF/n3Axceak4L60ZDQECQhGew=";
      npmBuild = "npm run build";
      npmInstallFlags = [ "--omit dev" ];
      installPhase = ''
        mkdir $out
        cp -r build/* $out
        cp package.json $out
        cp package-lock.json $out
      '';

Lily Foster: could you help me with packaging my nodejs app? These are the requirements:

*First,

You will need the output directory, the project's package.json, and the production dependencies in node_modules to run the application. Production dependencies can be generated by copying the package.json and package-lock.json and then running npm ci --omit dev (you can skip this step if your app doesn't have any dependencies). You can then start your app with this command:

node build
Development dependencies will be bundled into your app using Rollup. To control whether a given package is bundled or externalised, place it in devDependencies or dependencies respectively in your package.json.*

This is what I have:

buildInputs = with pkgs; [
        nodejs_20
      ];
      src = ./.;
      npmDepsHash = "sha256-mTpjBKTIJkYVj2jrH5lF/n3Axceak4L60ZDQECQhGew=";
      npmBuild = "npm run build";
      npmInstallFlags = [ "--omit dev" ];
      installPhase = ''
        mkdir $out
        cp -r build/* $out
        cp package.json $out
        cp package-lock.json $out
      '';