!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

206 Members
59 Servers

Load older messages


SenderMessageTime
30 Jul 2023
@lily:lily.flowersLily Foster When you try to builtins.readFile or import from the result of a derivation (like a fetched FOD) 01:14:13
@hexa:lossy.networkhexawhen one derivation needs to wait for the result of another derivation01:14:14
@hexa:lossy.networkhexasomething that's explicitly disabled on hydra01:14:23
@hexa:lossy.networkhexathere are a few more functions that import under the hood https://nixos.wiki/wiki/Import_From_Derivation#Recognizing_IFD01:15:14
@hexa:lossy.networkhexait will work for you locally, and that's what makes it tricky 🙂01:17:36
@gdamjan:spodeli.orggdamjanheh01:17:44
@gdamjan:spodeli.orggdamjan ok. let me try again the stdenv.mkDerivation path then 01:19:57
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
it will work for you locally, and that's what makes it tricky 🙂
I mean, it won't work for you locally anymore if you add --no-allow-import-from-derivation to the nix command (which is just what ofborg does iirc)
02:27:20
@gdamjan:spodeli.orggdamjan
In reply to @gdamjan:spodeli.org
ok. let me try again the stdenv.mkDerivation path then
https://gist.github.com/gdamjan/08901abe49baadf083034e93ed32ccbe#file-default-2-nix
I have no idea how kosher this is ^
03:09:48
@gdamjan:spodeli.orggdamjan(ignore that I use my fork, that was to prune some additional deps)03:10:17
@gdamjan:spodeli.orggdamjan but yarnLock = "${src}/yarn.lock"; would still be a problem, no?
so I need to take yarn.lock and add it to nixpkgs ?
03:11:17
@gdamjan:spodeli.orggdamjangoing to sleep now ... see ya tomorrow03:13:06
@gdamjan:spodeli.orggdamjanthat's this change https://github.com/matrix-org/matrix-appservice-irc/pull/175803:13:59
@lily:lily.flowersLily Foster
In reply to @gdamjan:spodeli.org
but yarnLock = "${src}/yarn.lock"; would still be a problem, no?
so I need to take yarn.lock and add it to nixpkgs ?
Not for fetchYarnDeps because it doesn't use the path at eval time (no import or read or anything), it's only used build time
03:15:17
@lily:lily.flowersLily Foster
In reply to @gdamjan:spodeli.org
going to sleep now ... see ya tomorrow
Rest well 💤
03:15:43
@robert:funklause.dedotlambda

How can I figure out which dependency causes

thread '<unnamed>' panicked at 'non-git dependencies should have assosciated integrity', src/parse/mod.rs:142:22

in https://github.com/karma-runner/karma ?

05:02:43
@robert:funklause.dedotlambda *

How can I figure out which dependency causes

thread '<unnamed>' panicked at 'non-git dependencies should have assosciated integrity', src/parse/mod.rs:142:22

when packaging https://github.com/karma-runner/karma using buildNpmPackage?

05:05:29
@robert:funklause.dedotlambda

turns out it's due to this line in package.json:

{
  "devDependencies": {
    "karma": "."
  }
}
06:04:42
@h7x4:nani.wtfh7x4 joined the room.08:30:48
@lily:lily.flowersLily Foster
In reply to @robert:funklause.de

turns out it's due to this line in package.json:

{
  "devDependencies": {
    "karma": "."
  }
}
Oh hmm, I can probably make that work if npm allows that, but does npm really allow using a package as a dev dependency of itself?
10:50:19
@gdamjan:spodeli.orggdamjannpm - everything goes10:50:55
@gdamjan:spodeli.orggdamjanwhat's even the point of that10:51:12
@lily:lily.flowersLily Foster
In reply to @gdamjan:spodeli.org
what's even the point of that
I think given it's a test runner that it's probably to allow them to run their own tests with itself
10:53:22
@lily:lily.flowersLily FosterBut I imagine that would really only work when there are no lifecycle scripts that need to run to build the package (e.g. to run typescript compiler or something)10:54:27
@lily:lily.flowersLily Foster(Still surprised it allows it at all though)10:54:40
@gdamjan:spodeli.orggdamjan Lily Foster: executive decision time. stdenv.mkDerivation https://gist.github.com/gdamjan/08901abe49baadf083034e93ed32ccbe#file-default-2-nix
or try to hack around with mkYarnPackage and try to make https://gist.github.com/gdamjan/08901abe49baadf083034e93ed32ccbe#file-default-nix work ?
12:23:33
@lily:lily.flowersLily Foster
In reply to @gdamjan:spodeli.org
Lily Foster: executive decision time. stdenv.mkDerivation https://gist.github.com/gdamjan/08901abe49baadf083034e93ed32ccbe#file-default-2-nix
or try to hack around with mkYarnPackage and try to make https://gist.github.com/gdamjan/08901abe49baadf083034e93ed32ccbe#file-default-nix work ?
Why do you have to set the yarn config twice here? https://gist.github.com/gdamjan/08901abe49baadf083034e93ed32ccbe#file-default-2-nix-L71
12:25:08
@lily:lily.flowersLily Foster Also if you can use fixup-yarn-lock from prefetch-yarn-deps rather than fixup_yarn_lock from yarn2nix https://github.com/NixOS/nixpkgs/issues/240174 12:26:06
@gdamjan:spodeli.orggdamjanI don't know, but the yarn --production pruning tried to download without that (and failed because of the --ofline) 12:26:11
@gdamjan:spodeli.orggdamjanI'm guessing themktemp HOME was removed between the phases?12:27:01

Show newer messages


Back to Room ListRoom Version: 6