Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
cc @nodejs/undici |
Failed to start CInode:internal/modules/cjs/loader:1028
const err = new Error(message);
^
|
|
I'll take a look at the errors, seem to be related |
It's coming from nodejs/undici#2310 |
|
@KhafraDev @Ethan-Arrowood see the update script failing now https://github.com/nodejs/node/actions/runs/6486757082/job/17615604220#step:4:62 |
|
maybe we do need to use esbuild hooks |
|
v5.26.2 incoming with security patch. |
|
please just revert the user-agent changes entirely until the build steps are figured out. |
|
I'll be home in an hour and a half, we won't be able to land until the esbuild issues are fixed |
|
|
|
its cause its missing from the files list. adding now. releasing in 5.26.3 No. There is a separate bug in the update script in Node, I'm opening a PR as soon as it builds. |
|
The script is missing that was added to build it. I thought node would pull from the undici repo, not from npm. 😕 |
|
I believe both nodejs/undici@5351f1f and #50150 is needed if the script insists on pulling from npm and not git. |
|
I already reverted my change: nodejs/undici@81e0a93 in undici. and didn't release 5.26.3. I'll let you or Matteo take it from here. Feels like a too-many-cooks-in-the-kitchen situation. |
|
I'm really merely observing. My suggestion would be to revert to the previous build step and revert the user-agent changes entirely for now. You could use |
This is an automated update of undici to 5.26.0.