[pulsar-next] Cannot find module ../build/Release/git.node

[asiloisad]

Thanks in advance for your bug report!

• Have you reproduced issue in safe mode?
• Have you used the debugging guide to try to resolve the issue?
• Have you checked our FAQs to make sure your question isn't answered there?
• Have you checked to make sure your issue does not already exist?
• Have you checked you are on the latest release of Pulsar?

What happened?

Pulsar version

1.124.2025020900-next

Which OS does this happen on?

🐧 Debian based (Linux Mint, Ubuntu, etc.)

OS details

10

Which CPU architecture are you running this on?

x86_64/AMD64

What steps are needed to reproduce this?

1. Open settings
2. Go to Packages, Themes, Updates or Install

Additional Information:

No response

[savetheclocktower]

This feels like the sort of error that would happen when running from source, but not necessarily when running a packaged version. Can you do these things for me?

1. Make sure yarn install and yarn build complete successfully.
2. Run yarn dist --next to generate a bundle, then run it without a --dev flag, and see if the problem persists.

[asiloisad]

It's opposite. Local build works fine, but a packaged version has issue.

[asiloisad]

I have tested a build before and it's works fine 7920195. An issue has been introduce there 2ee0b6f probably. Reinstall of 1.124.2025020900-next doesn't help.

[savetheclocktower]

I have tested a build before and it's works fine 7920195. An issue has been introduce there 2ee0b6f probably. Reinstall of 1.124.2025020900-next doesn't help.

How lovely! That makes zero sense whatsoever, so this will be a fun one to chase down.

[asiloisad]

I'm not sure is it related. Dev tools of 1.124.2025020900-next report error of failed fetching. It doesn't popup in 1.124.2025012818-next.

A tabs Updates and Themes report this:

A tab Packages report this:

[savetheclocktower]

Can you try running some ppm-next commands from your shell? See if ppm-next outdated produces the same error.

[asiloisad]

oh, It look like ppm-next is totally broken

[savetheclocktower]

OK, this feels closer to the root symptom. No idea why it's happening, but I bet it could have something to do with a missed (or failed) compilation step during the build. You say it works fine when run from source, so I'll see if I can reproduce this from nightly PulsarNext builds on Windows.