!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

206 Members
59 Servers

Load older messages


SenderMessageTime
15 Dec 2023
@lily:lily.flowersLily Fosterit's not exactly a nix problem that hugo needs a working HOME but their recommended security policies for babel don't include that13:35:43
@lily:lily.flowersLily Fosterunless i just missed it when skimming hugo docs13:35:50
@lily:lily.flowersLily Foster* it's not exactly a nix problem that babel needs a working HOME but the hugo recommended security policies for babel don't include that13:36:21
@avocadoom:avocadoom.deavocadoomguess I'll just open an issue and see where it goes then13:43:16
@avocadoom:avocadoom.deavocadoommaybe this is an oversight and they can make it a default or something like that13:43:28
@shine:proqqul.netTaeer Bar-Yam joined the room.14:54:36
18 Dec 2023
@platonic.mason:matrix.orgMason Mackaman joined the room.08:51:00
@platonic.mason:matrix.orgMason Mackamanwhat is the current best tools for the job in this department? npmlock2nix was my go to a year ago, but now it's not working for me. I'm trying to rangle dream2nix but I'm not liking the UX so far, and certain things are just now working such that I've had to patch the code for my stuff to build. so yeah, I'm wondering if there have been any other tools introduced since last I have needed to tackle this horrible problem.08:53:34
@platonic.mason:matrix.orgMason Mackaman * what is the current best tools for the job in this department? npmlock2nix was my go to a year ago, but now it's not working for me. I'm trying to rangle dream2nix but I'm not liking the UX so far, and certain things are just not working such that I've had to patch the code for my stuff to build. so yeah, I'm wondering if there have been any other tools introduced since last I have needed to tackle this horrible problem.08:53:55
@whentze:matrix.orgWanja Hentze

here's my view:

  • npmlock2nix: worked okay, but undermaintained and never got lockfile v3 support
  • buildNpmPackage (from nixpkgs): works fine, but needs prefetching. makes one big derivation for deps and is thus slow for small dep changes
  • dream2nix: too complicated, couldn't get it to work
  • floco: too complicated, couldn't get it to work
  • adisbladis' buildNodeModules: worked great and looks simple, needs no prefetcher. is very very alpha stage software though
08:58:55
@whentze:matrix.orgWanja Hentzethings I've yet to check out: serokell/nix-npm-buildpackage, napalm09:00:34
* @adis:blad.is@adis:blad.is should put buildNodeModules in nixpkgs09:07:12
@whentze:matrix.orgWanja Hentzedo ittt09:08:12
@sandro:supersandro.deSandro ๐ŸงDidn't it require to always commit package.json or the lock file to do IFD?13:06:58
@sandro:supersandro.deSandro ๐ŸงIf it is without IFD or coming lock files and really just works, we should just use it for everything. We shouldn't really have multiple ways to build things if one thing is superior13:07:40
@whentze:matrix.orgWanja Hentzeyes it does13:08:50
@whentze:matrix.orgWanja Hentzethe asymmetry here is from nixpkgs-internal vs. external use13:09:05
@whentze:matrix.orgWanja Hentzefor external stuff that's consuming nixpkgs, having the package.json and package-lock.json committed is actually totally fine13:09:34
@whentze:matrix.orgWanja Hentzenow, should nixpkgs export packaging helpers that it doesn't even want to use for itself? maybe, maybe not13:10:17
@whentze:matrix.orgWanja Hentzefwiw I'm kinda salty that poetry2nix got removed because it wasn't used internally anymore.13:10:57
@whentze:matrix.orgWanja Hentzedownstream repos have their own lockfiles committed anyway. but they might want to update deps more often, so an expensive prefetch step is more of a problem than it is for nixpkgs13:12:52
@sandro:supersandro.deSandro ๐Ÿง
In reply to @whentze:matrix.org
fwiw I'm kinda salty that poetry2nix got removed because it wasn't used internally anymore.
It got removed because it was broken after the bootstrapping changed and it wasn't fixed for some time
13:47:58
@sandro:supersandro.deSandro ๐ŸงAlso vendoring other git repos into the tree is mรคh13:48:16
@sandro:supersandro.deSandro ๐Ÿง
In reply to @whentze:matrix.org
for external stuff that's consuming nixpkgs, having the package.json and package-lock.json committed is actually totally fine
But it is really, really fat
13:48:50
@sandro:supersandro.deSandro ๐ŸงWe can't just xz compress them and then commit them? ๐Ÿ˜…13:49:12
@whentze:matrix.orgWanja HentzeI think you're misunderstanding me13:49:29
@whentze:matrix.orgWanja HentzeI'm not saying let's commit a bunch of lockfiles to nixpkgs13:49:41
@whentze:matrix.orgWanja Hentze the use case is "I have a nodejs project and my lockfile is already in git, I want to write a default.nix" 13:50:28
@whentze:matrix.orgWanja Hentzethis has nothing to do with nixpkgs other than that it would be nice to get the packaging helper function from nixpkgs13:51:48
@whentze:matrix.orgWanja Hentzehence me asking "is it worthwhile to ship packaging helpers in nixpkgs that are not dogfooded by nixpkgs?"13:53:33

Show newer messages


Back to Room ListRoom Version: 6