Amin Ya

> Shouldn't this PR be retargeted to traversaro:movespecification, because it is basically an extension of it? The purpose here is improving the specification while the other PR's main goal was...

If it fails to open, the issue is Wayland. See the solution here: https://github.com/warpdotdev/Warp/issues/5367#issuecomment-2408890422

No, I don't have a simpler reproduction. Parcel also uses Nodejs Add-on API, so @devongovett should be able to help add a reproduction with a debug build of Parcel

Here's the log with `NODE_DEBUG=*` ``` node ./node_modules/parcel/bin/parcel.js ``` [errors.log](https://github.com/user-attachments/files/16753803/errors.log) Looks like Parcel's caching code triggers this. ``` @[email protected]_@[email protected]_@[email protected]_/node_modules/@parcel/cache/lib/FSCache.js] ``` https://github.com/parcel-bundler/parcel/blob/0e08d8c69243e104aaba52c2393d528bb6872450/packages/core/cache/src/FSCache.js

> 👋 Hey, v22.8.0 was just released, is this reproducible in that version? Yes, the parcel builds still fail on Node 22.8.0

I found the function that triggers this error in Nodejs. It seems it was changed last week in a commit to update V8: https://github.com/nodejs/node/blame/4f1c27af8c09c45ac7dcb7c48146aa9392cebde8/deps/v8/src/ic/ic.cc#L251 This is where the error actually...

The workaround for this is to specify `isLibrary: true` in the package.json for the target.

For me doesn't seem to load at all. I just upgraded from Ubuntu 24.04 to Ubuntu 24.10, and warp refuses to start. There's no log when calling `warp-terminal` Edit: Surprisingly,...

I realized that the terminal loads instantly if I use `sudo`. The issue seems to be related to the current user. ``` sudo warp-terminal ```

Ok, found an actual solution. The issue happens because Warp fails to open under Wayland. So you have to force Warp to use Xwayland instead. ```shell pkill warp WAYLAND_DISPLAY=, warp-terminal...