| 12 Nov 2023 |
 peter-lustig | should have just done what the docs say | 14:09:00 |
| peter-lustig | and not try own stuff xd | 14:09:05 |
 Lily Foster | possibly | 14:09:39 |
| Lily Foster | i did admittedly steer you away from that since i figured if they would use rollup, they were bundling deps | 14:09:50 |
| Lily Foster | so, i do apologize for that | 14:09:56 |
| Lily Foster | (also the docs didn't make any sense) | 14:10:04 |
| Lily Foster | (as well) | 14:10:10 |
| peter-lustig | this is all weird as hell | 14:10:22 |
| Lily Foster | pretty much sums up how i'm feeling about sveltekit at this point | 14:10:34 |
| Lily Foster | (it's almost like they never expected it to be used outside of dev and in production) | 14:10:49 |
| peter-lustig | In reply to @lily:lily.flowers
(it's almost like they never expected it to be used outside of dev and in production) feels more like they just want to force you to use netlify or vercel | 14:11:13 |
| Lily Foster | or that, yeah | 14:11:24 |
| peter-lustig | anyways, I will never touch this crap again | 14:11:39 |
| peter-lustig | well first have to try if the systemd service works now | 14:11:49 |
 szucsitg | I personally don't like yarn, but it'd be a significant undertaking to move to npm, this an old and slightly messy project | 14:12:38 |
| Lily Foster | understood | 14:12:45 |
| szucsitg | * I personally don't like yarn, but it'd be a significant undertaking to move to npm, this is an old and slightly messy project | 14:12:48 |
| Lily Foster | i might have to see more of the package.json files though to better understand what you're needs are | 14:13:06 |
| peter-lustig | i feel like yarn makes everything more complicated if you do nix stuff | 14:13:18 |
| Lily Foster | In reply to @peter-lustig:matrix.org
i feel like yarn makes everything more complicated if you do nix stuff (tbh that's on the nix side. yarn seems decent otherwise, but we don't have good yarn tooling yet and yarn2nix is, uh, a bit questionable) | 14:14:10 |
| Lily Foster | (pnpm seems better though so honestly i'd rather have pnpm tooling at this point...) | 14:14:28 |
| peter-lustig | In reply to @lily:lily.flowers
(tbh that's on the nix side. yarn seems decent otherwise, but we don't have good yarn tooling yet and yarn2nix is, uh, a bit questionable) I just stay away from every single third party project that has to do with packaging, it makes everything so much more complicated | 14:15:47 |
| szucsitg | In reply to @lily:lily.flowers
i might have to see more of the package.json files though to better understand what you're needs are Do you think that instead of "manually" parsing the packages I should try mkYarnWorkspace to do it for me. What puzzles me that all workspace packages are symlinked to offlineCache node-modules but my project somehow cannot find it during build | 14:16:14 |
| Lily Foster | at this point i just wanna stay away from nodejs, but, uh, i feel that's probably not an option | 14:16:17 |
| Lily Foster | In reply to @szucsitg:matrix.org
Do you think that instead of "manually" parsing the packages I should try mkYarnWorkspace to do it for me. What puzzles me that all workspace packages are symlinked to offlineCache node-modules but my project somehow cannot find it during build i've never used mkYarnWorskpace. it might be perfect though! I'd have to check | 14:16:37 |
| Lily Foster | In reply to @szucsitg:matrix.org
Do you think that instead of "manually" parsing the packages I should try mkYarnWorkspace to do it for me. What puzzles me that all workspace packages are symlinked to offlineCache node-modules but my project somehow cannot find it during build offlineCache and node_modules are different | 14:16:54 |
| Lily Foster | like, one is a yarn download cache | 14:17:05 |
| Lily Foster | and the other is built dependencies | 14:17:10 |
| Lily Foster | * and the other is built dependencies in a NODE_PATH layout | 14:17:19 |
| peter-lustig | everything works now, the systemd service and the nginx proxypass to redirect the domain there :) | 14:19:35 |
