!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

210 Members
62 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

Show newer messages


Back to Room ListRoom Version: 6