In reply to @matejam:matrix.org
Here's a working version: https://github.com/MatejaMaric/yota-laravel/blob/c114ebc3c725a67a19d148a95543ed307094c659/derivation.nix
Thanks a lot Lily! 🤗

In reply to @matejam:matrix.org
Here's a working version: https://github.com/MatejaMaric/yota-laravel/blob/c114ebc3c725a67a19d148a95543ed307094c659/derivation.nix
Thanks a lot Lily! 🤗

In reply to @c0ba1t:matrix.org
Iirc, the nodejs 22 LTS has some problems with node gyp. You might want to stick with 18 for a few more weeks until testing has been done

In reply to @c0ba1t:matrix.org
Iirc, the nodejs 22 LTS has some problems with node gyp. You might want to stick with 18 for a few more weeks until testing has been done

(if you want, you can set npmBuildScript = "prod" and include npmBuildHook as well and remove the postBuild)

Hm, for some reason if I do that it doesn't generate files that npm run prod generates in $src/share/php/yota-laravel/public/ where I want them.

In reply to @matejam:matrix.org

(if you want, you can set npmBuildScript = "prod" and include npmBuildHook as well and remove the postBuild)

Hm, for some reason if I do that it doesn't generate files that npm run prod generates in $src/share/php/yota-laravel/public/ where I want them.

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

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

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

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

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

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

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

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

In reply to @c0ba1t:matrix.org
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.

In reply to @c0ba1t:matrix.org
I'll try to make a PR when 20.0.1 gets released.