electron: Electron 35 "Cannot find package" regression
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for a bug report that matches the one I want to file, without success.
Electron Version
35.0.0
What operating system(s) are you using?
Other Linux
Operating System Version
Linux debian 5.10.0-18-arm64 #1 SMP Debian 5.10.140-1 (2022-09-02) aarch64 GNU/Linux
What arch are you using?
arm64 (including Apple Silicon)
Last Known Working Electron version
34.3.0
Expected Behavior
Launching the app works.
Actual Behavior
Launching the app fails with uncaught exception “Cannot find package”
Testcase Gist URL
No response
Additional Information
The auto-launch dependency is a fairly common one in the Electron space, and the file the error talks about auto-launch/dist/index.js is present in the ASAR.
As the earlier screenshots show, the same app.asar works with v34, but not with v35.
Based on automated tests in https://github.com/element-hq/element-desktop/pull/2195 it affects Windows, Mac & Linux across both amd64 & aarch64.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 6
- Comments: 15 (3 by maintainers)
There’s a hypothesis that this might be related to https://github.com/electron/electron/pull/45878.
FWIW, we are facing the same issue with an Electron app that uses electron-updater when we try to use electron 35:
I can confirm this bug! Here it happens with the following ESM packages:
electron-debug electron-context-menu electron-is-dev (uncertain with the last one but the first two are 100% broken)
All worked just fine with electron 34 to which we have to revert to, as this bug completely crashed our app and took some time to lead the root cause to the ESM flavor of the packages here.
I hope this can be fixed soon 😃 Thanks for your ongoing effort and support 😃
@mtdvlpr It shows up on npm for me now: https://www.npmjs.com/package/electron/v/35.0.2
Unclear. That’s the one that trips when testing Element Desktop against v35. Its possible removing it would just explode elsewhere but I haven’t had the opportunity to test, I focused my time on the repro instead.