| 10 Nov 2023 |
 daniel | * I'm successfully deploying a SvelteKit project without issues using buildNpmPackage, can be seen here for reference: https://github.com/danielalvsaaker/tf-viewer-net/blob/main/frontend/default.nix | 22:56:55 |
 peter-lustig | In reply to @lily:lily.flowers
so yeah i guess you could just change the makeWrapper to this:
makeWrapper ${pkgs.nodejs-slim_20}/bin/node $out/bin/sveltepackage \
--add-flags --env-file=.env \
--add-flags $out/lib/node_modules/sveltepackage
do I need that wrapper? | 22:57:43 |
 Lily Foster | i guess you don't need it | 22:58:10 |
| daniel | * I'm successfully packaging a SvelteKit project without issues using buildNpmPackage, can be seen here for reference: https://github.com/danielalvsaaker/tf-viewer-net/blob/main/frontend/default.nix | 22:58:10 |
| Lily Foster | i assumed you wanted something to run it like the sveltekit docs were suggesting | 22:58:20 |
| peter-lustig | In reply to @lily:lily.flowers
i assumed you wanted something to run it like the sveltekit docs were suggesting basically, my goal is to just get it with inputs.sveltekit-package.${pkgs.system}.default; and it does all the stuff. I run it on nginx | 22:59:51 |
| peter-lustig | then I would just set the proxypass and it communicates with the db and done | 23:00:20 |
| peter-lustig | that is the plan at least | 23:00:29 |
