!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

210 Members
61 Servers

Load older messages


SenderMessageTime
13 Nov 2023
@lily:lily.flowersLily Foster apparently npm prunes deps but then decides that the node_modules/@pulumi/query (that already has been reified when deps were built) is insufficient and needs to be re-reified. which would be fine except it also decides that the cache is for losers and ignores or otherwise gets too spooked by the existing entry for query-0.3.0.tgz 17:27:43
@lily:lily.flowersLily Fosterwhic17:28:00
@lily:lily.flowersLily Foster * which17:28:01
@lily:lily.flowersLily Fostermakes no sense17:28:03
@lily:lily.flowersLily Foster npm is very eager to silently get spooked and redownload though so i'm ultimately not surprised 17:28:21
@lily:lily.flowersLily Fosterit would be nice to know whether it got spooked or didn't try the cache to begin with though (and even npm's debug logging does not log a lot of the situations where it gets spooked and bails for, unfortunately)17:28:54
@keiichi:matrix.org@keiichi:matrix.orgdontNpmPrune "fixed" the build ty for help I hope this helps improving the understanding of npm xD17:30:03
@lily:lily.flowersLily Fosteri'm trying to root out the bug now17:33:18
@lily:lily.flowersLily Fosterin npm17:33:20
@lily:lily.flowersLily Fosterwhich upstream will invariably ignore a PR for but oh well17:33:28
@lily:lily.flowersLily Foster okay so npm is actually just removing the cache value from npmrc? 17:39:14
@lily:lily.flowersLily Fosterwhat the hell?17:39:15
@lily:lily.flowersLily Fosteroh we actually remove that17:39:50
@lily:lily.flowersLily Fosterin the hook17:39:51
@lily:lily.flowersLily Fosterthe bugs are coming from inside the nixpkgs17:39:56
@lily:lily.flowersLily Fosterokay17:39:57
@lily:lily.flowersLily Fosterwell give me a bit and i'll be able to have a "fix" for that17:40:10
@lily:lily.flowersLily Foster(it is probably bug on our end, but npm still shouldn't be trying to re-reify stuff regardless when pruning)17:40:25
@lily:lily.flowersLily Foster * (it is probably partly a bug on our end, but npm still shouldn't be trying to re-reify stuff regardless when pruning)17:40:35
@lily:lily.flowersLily Foster teto: can you try from github:lilyinstarlight/nixpkgs/fix/npm-pack-shenanigans and see if that works without compromising prune? 17:44:51
@keiichi:matrix.org@keiichi:matrix.org awesome. There is no hurry on my side since dontNpmPrune works well. Now there is one question I've asked on the discourse without any answer is how people work with typescript on nix ? I had solved it with dream2nix but with the rewrite I stopped using it and I would like to use buildNpmPackage since it works reasonably well. Usually in my shellHook, I export NODE_PATH=${drvBuiltBy_buildNpmPackage}/lib/node_modules but typescript ignores NODE_PATH I believe so I end with TSError: ⨯ Unable to compile TypeScript: and index.ts(1,25): error TS2307: Cannot find module '@pulumi/pulumi' or its corresponding type declarations. 17:45:42
@keiichi:matrix.org@keiichi:matrix.orgI'll have to merge that in my own nixpkgs. Gotta do some shopping before it closes than I try ty !17:46:29
@lily:lily.flowersLily Foster
In reply to @keiichi:matrix.org
awesome. There is no hurry on my side since dontNpmPrune works well. Now there is one question I've asked on the discourse without any answer is how people work with typescript on nix ? I had solved it with dream2nix but with the rewrite I stopped using it and I would like to use buildNpmPackage since it works reasonably well. Usually in my shellHook, I export NODE_PATH=${drvBuiltBy_buildNpmPackage}/lib/node_modules but typescript ignores NODE_PATH I believe so I end with TSError: ⨯ Unable to compile TypeScript: and index.ts(1,25): error TS2307: Cannot find module '@pulumi/pulumi' or its corresponding type declarations.
It should "just work" for the most part. Is there a reproducer on the discourse post? (feel free to tag me on those btw, i don't watch discourse super closely)
17:46:33
@lily:lily.flowersLily Foster
In reply to @keiichi:matrix.org
I'll have to merge that in my own nixpkgs. Gotta do some shopping before it closes than I try ty !
okay, sounds good! let me know when you try it
17:46:49
@lily:lily.flowersLily Foster (i did just try it with the derivation and package{,-lock}.json files you posted above and it does seem to work with the above patch. i will PR it imminently but i'm gonna see if i can convince someone to merge https://github.com/NixOS/nixpkgs/pull/254420 first so i don't have to worry about merge conflicts since they both modify the same line) 18:01:35
@keiichi:matrix.org@keiichi:matrix.org Lily Foster: I've just tested it and it fixed it \o/ 20:21:28
@keiichi:matrix.org@keiichi:matrix.orgjust found my initial post, still valid https://discourse.nixos.org/t/help-typescript-to-find-modules/2685121:06:33
@ambroisie:belanyi.fr@ambroisie:belanyi.fr Hey 👋
Does anyone here with more knowledge about our JS build helpers know why I need to do the whole dance with substituteAll in this MR, or rather if there's a better fix?
The vite.config.ts for reference, which sets up a bunch of file copies which fail if I don't fix the paths
22:48:59
@lily:lily.flowersLily Foster
In reply to @ambroisie:belanyi.fr
Hey 👋
Does anyone here with more knowledge about our JS build helpers know why I need to do the whole dance with substituteAll in this MR, or rather if there's a better fix?
The vite.config.ts for reference, which sets up a bunch of file copies which fail if I don't fix the paths
yarn2nix does weird stuff but idk why exactly you're needing that here. i doubt there's a better fix than that though
22:51:05
@lily:lily.flowersLily Foster(i still want to yeet yarn2nix into the abyss at some point once we have mature and modern yarn tooling)22:51:34

Show newer messages


Back to Room ListRoom Version: 6