question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Announcement] V2.0 beta stability poll

See original GitHub issue

Hello everyone👋! I’m getting ready to move the 2.0 beta to RC (release candidate) status as it is long overdue, but I first want to make sure that there aren’t any breaking changes requested. If you think that the 2.0 beta is ready for RC then please 👍 this issue. If not, please 👎 and leave a comment explaining why.

Specifically, I’d like feedback on the following major changes:

  • Is the new spectron testing process preferred over the old one? Does anyone have any suggestions for improvement?
  • Does it make sense to disable node integration by default? This means that apps will likely be more secure, but native modules and other electron-provided functions will not work without configuring nodeIntegration.
  • Has it been stable for you? Are there any new bugs that have popped up?
  • Is the migration guide on the release announcement sufficient? Were there any additional changes you had to make? Did it all go smoothly?

Thanks for all your feedback!

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:16
  • Comments:28 (13 by maintainers)

github_iconTop GitHub Comments

3reactions
aleksey-hoffmancommented, Apr 30, 2020

I think electron-builder should not have node integration disabled by default. By messing with Electron properties it adds an unnecessary complication layer. All Electron settings should be in 1 place - in the main Electron process - so that when you need to change things like node integration you didn’t have to waste time figuring out where’s what and why does electron-builder docs conflict with Electron docs. And what if I need to disable it only for 1 renderer but not the other ones? Will it override webPreferences.nodeIntegration of every window? People will flood you and the Electron repo with questions asking why don’t their modules work anymore.

Please don’t add unnecessary complexity layers.

2reactions
nklaymancommented, Jun 13, 2020

Yes, I’d love for this plugin to support vue 3. I’ll take a look at it sometime this week probably.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Android 11 Beta 2 and Platform Stability
With the platform now stable, we're encouraging all app and game developers to start your final compatibility testing and publish your updates ...
Read more >
What's new - Flutter documentation
For more information, see Announcing Flutter 2, What's new in Flutter 2, Flutter web support hits the stable milestone, Announcing Dart 2.12, and...
Read more >
It's here: please welcome Arduino IDE 2.0
We're pleased to announce that as of today Arduino IDE 2.0 has moved to stable and is available for download. Since the launch...
Read more >
Hotfixes to the Stable Channel · flutter/flutter Wiki - GitHub
This hotfix release addresses the following issue: flutter/77173 - Building for macOS target fails when Flutter is installed from website. 2.0.0 (March 3, ......
Read more >
Blog - Next.js 13
As we announced at Next.js Conf, Next.js 13 (stable) lays the foundations to be dynamic without limits: app Directory (beta): Easier, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found