Skip to content

Conversation

gwleuverink
Copy link
Contributor

@gwleuverink gwleuverink commented Sep 5, 2025

Fixes NativePHP/laravel#390

This PR updates to the latest versions of Electron & ChromeDriver

The Menubar package was blocking the update before. So I had to pull it in as a vendored library as suggested here #233 (comment)


This update introduces some breaking changes

https://www.electronjs.org/docs/latest/breaking-changes#planned-breaking-api-changes-340
https://www.electronjs.org/docs/latest/breaking-changes#planned-breaking-api-changes-350
https://www.electronjs.org/docs/latest/breaking-changes#planned-breaking-api-changes-360
https://www.electronjs.org/docs/latest/breaking-changes#planned-breaking-api-changes-370
https://www.electronjs.org/docs/latest/breaking-changes#planned-breaking-api-changes-380

Most notably dropping support for macOS Catalina & Big Sur. I don't think the other things affect us, would appreciate double verification on that 🙏🏻

gwleuverink and others added 13 commits September 5, 2025 10:25
rollup would create another level of nesting which required to change imports in multiple places. I'd rather not touch any other imports for this change. Moving everything inside the plugin src directory has the least impact across unrelated files
…' of github.com:NativePHP/electron into chore/pull-in-blocking-menubar-lib-and-upgrade-electron
…' of github.com:NativePHP/electron into chore/pull-in-blocking-menubar-lib-and-upgrade-electron
@gwleuverink gwleuverink changed the title Chore/pull in blocking menubar lib and upgrade electron Chore/ Update Electron & Chromedriver to v38 Sep 5, 2025
@gwleuverink gwleuverink changed the title Chore/ Update Electron & Chromedriver to v38 Chore/ Update Electron & ChromeDriver to v38 Sep 5, 2025
@gwleuverink gwleuverink marked this pull request as ready for review September 5, 2025 15:03
@gwleuverink gwleuverink requested review from simonhamp and a team September 5, 2025 15:03
@gwleuverink
Copy link
Contributor Author

gwleuverink commented Sep 5, 2025

I put the vendored libraries in resources/js/libs at first. But due to how the plugin is built it placed the transpiled files in a different directory structure. Because of that I was forced to update import paths in multiple places, unrelated to the update.

That's why I opted to put the vendored libs in resources/js/electron-plugin/src instead. This way I only had to modify 1 import.

Copy link
Member

@simonhamp simonhamp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, but I think when we release this it will need to be a v2. These breaking changes feel like something we need to call out pretty clearly

@gwleuverink
Copy link
Contributor Author

Agreed 💯

@gwleuverink gwleuverink added the v2 label Sep 10, 2025
@gwleuverink gwleuverink self-assigned this Sep 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update the Electron package dependencies
3 participants