!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

202 Members
58 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
30 Apr 2024
@lily:lily.flowersLily Foster
In reply to @lily:lily.flowers
oh you know what
i wonder if it's because the composer stuff changes build to that dir first
21:02:06
@lily:lily.flowersLily Fosterif it's working now, leave it as-is then :)21:02:13
@matejam:matrix.orgmatejam

i wonder if it's because the composer stuff changes build to that dir first

Yeah, maybe even the other way around. In the logs I see first the npm runs and then composer>

if it's working now, leave it as-is then :)

sure 😄

share derivation? (e.g. on a pastebin?) that seems weird

If you are interested, I can make a new branch with the change. It's my open source project anyway

21:04:59
@matejam:matrix.orgmatejam *

i wonder if it's because the composer stuff changes build to that dir first

Yeah, maybe even the other way around. In the logs I see first the npm runs and then composer.

if it's working now, leave it as-is then :)

sure 😄

share derivation? (e.g. on a pastebin?) that seems weird

If you are interested, I can make a new branch with the change. It's my open source project anyway

21:05:17
@lily:lily.flowersLily Foster
In reply to @matejam:matrix.org

i wonder if it's because the composer stuff changes build to that dir first

Yeah, maybe even the other way around. In the logs I see first the npm runs and then composer.

if it's working now, leave it as-is then :)

sure 😄

share derivation? (e.g. on a pastebin?) that seems weird

If you are interested, I can make a new branch with the change. It's my open source project anyway

nah, i'm pretty sure it's because composer changes dir and you want npm to run after that. so you're doing it right enough and this looks pretty awesome actually :)
21:05:34
@lily:lily.flowersLily Fosterit feels neat that you are able to mix the npm hooks into another builder without too much fuss and have a multi-language-package-manager app build in a derivation like that21:06:10
@lily:lily.flowersLily Foster
In reply to @c0ba1t:matrix.org
Iirc, it is on 22 on unstable. I don't remember the specifics but an unstable bum recently made our builds fail until we returned to 18. Iirc, it was similar to https://github.com/nodejs/node-gyp/issues/3029
oooof. well marsam left and i'm recovering from surgery, so someone else will probably have to bump the nodejs derivation
21:09:32
@lily:lily.flowersLily Foster
In reply to @lily:lily.flowers
oooof. well marsam left and i'm recovering from surgery, so someone else will probably have to bump the nodejs derivation
(no one else is on nodejs team rn except winter who also hasn't had time for things....)
21:10:15
@matejam:matrix.orgmatejam Yeah, Composer also has it's own version of fetchNpmDeps (mkComposerRepository) but I couldn't really make it work. I don't know how it would handle 3 or more language app builds 😂 I'm glad that it works for 2 21:10:14
@c0ba1t:matrix.orgCobalt
In reply to @lily:lily.flowers
oooof. well marsam left and i'm recovering from surgery, so someone else will probably have to bump the nodejs derivation
It looks like the fix for the upstream issue was merged today. Though, by the comments on the MR, it will likely take a bit until a patch release will be published. So there's no need to hurry here.
21:27:35

Show newer messages


Back to Room ListRoom Version: 6