| 10 Nov 2023 |
 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 |
| Lily Foster | What's it there? Like do you want a script to run it? (like the wrapper makes?) | 23:01:44 |
| peter-lustig | In reply to @lily:lily.flowers
What's it there? Like do you want a script to run it? (like the wrapper makes?) yes, I guess it needs to somehow run permanently. SvelteKit docs say: You can then start your app with this command: node build | 23:03:25 |
| Lily Foster | yeah the wrapper would replace that | 23:03:57 |
| Lily Foster | and do that for you | 23:04:00 |
| Lily Foster | but like, you'd still have to start the wrapper somehow | 23:04:16 |
| Lily Foster | If it's nixos, just making it a systemd service would be easiest, but otherwise you could come up with something else | 23:04:42 |
| peter-lustig | how do I start the wrapper with systemd | 23:05:03 |
| peter-lustig | problem is i do not even understand the wrapper | 23:05:15 |
| peter-lustig | all of this is black magic to me right now | 23:06:23 |
| Lily Foster | It is a shell script that basically makes a file in ${drv}/bin/sveltepackage and that shell script does ${nodejs-slim_20}/bin/node ${drv}/lib/node_modules/sveltepackage (which is where the above derivation moved build to) | 23:06:28 |
| Lily Foster | so it is effectively a node build that doesn't have environment requirements that like node is in PATH or build is in current working directory and such | 23:06:57 |
| Lily Foster | (so you don't need to do more than just run the wrapper. since node build would require a bunch of environment nonsense to get to work) | 23:07:20 |
| Lily Foster | Sorry i'm not great at explaining rn :( | 23:07:45 |
| peter-lustig | In reply to @lily:lily.flowers
Sorry i'm not great at explaining rn :( Could you maybe help me later? I also have some more questions | 23:08:40 |
| peter-lustig | Because I worked for too long today, tired | 23:08:51 |
| Lily Foster | Sure! Later is fine | 23:08:58 |
| Lily Foster | (assuming later means tomorrow, that'll probably be better for me too) | 23:09:07 |
| peter-lustig | yes :) | 23:09:18 |
| peter-lustig | I ping you then, thanks | 23:09:22 |
| Lily Foster | In reply to @janne.hess:helsinki-systems.de
Full reproducer with the original files: https://github.com/dasJ/broken-npm-test frontend-npm-deps> [2023-11-10T23:15:37Z DEBUG isahc::handler] Could not resolve host: 16.0.0-beta.8
Hmmmm it really doesn't like this and assumes it's a tarball url i think? https://github.com/dasJ/broken-npm-test/blob/8c6d8ed9b180a66a81b133f68bf467e12bcbe3be/package-lock.json#L2817
| 23:18:12 |
| Lily Foster | i'll try to look at it later and might have a fix | 23:18:27 |
 @janne.hess:helsinki-systems.de | ah didn't spot that | 23:22:55 |
| @janne.hess:helsinki-systems.de | strange | 23:23:01 |
