My build script (left the hash out for abbreviation):

packages.${system}.default = pkgs.buildNpmPackage {
      name = "project-build";
      src = ./.;
      installPhase = ''
        mkdir $out
        cp -r build/* $out
        cp package.json $out
        cp -r node_modules $out
      '';
    };
  };

In reply to @peter-lustig:matrix.org

>     at VariableDeclarator.bind (file:///build/2rdr2hwic3kd9pwpgp32s206yh5kqwhs-source/node_modules/rollup/dist/es/shared/node-entry.js:4639:23)
       >
       > ERROR: `npm build` failed

Is this some nix issue again?

I can build the project fine with npm run build

In reply to @lily:lily.flowers
hmmm it's unclear. can you send full build output? the error is before that

In reply to @peter-lustig:matrix.org
it does not happen when I do npm run build without nix stuff

In reply to @lily:lily.flowers
yeah but do you have github env vars set?

In reply to @lily:lily.flowers
you can mock up fake ones in the nix build too

In reply to @peter-lustig:matrix.org
could you show me how I would do that in my current flake

you can do something like this though:

env = {
    GITHUB_CLIENT_ID = "";
    GITHUB_CLIENT_SECRET = "";
    ...
}

In reply to @lily:lily.flowers
(dynamically grabbing them from the env when they are needed rather than importing from a virtual module would probably be more robust, and would also handle things like the env vars changing during the lifetime of the program better)

yeah i had it dynamic before and everything worked, but look at this:

https://kit.svelte.dev/docs/migrating-to-sveltekit-2#dynamic-environment-variables-cannot-be-used-during-prerendering