[BUG] Electron 14+ does not work with @nestjs/common
See original GitHub issueContext:
- Playwright Version: 1.24.*
- Operating System: Windows
- Node.js version: 16.10 +
- Browser: Chrome
Code Snippet electronApp = await electron.launch({ args: [path.join(__dirname, ’ ****')], bypassCSP: true }); app1stWindow= await electronApp.firstWindow();
**Describe the bug**
**Electron 12 has been EOL, so i migrate the electron app to electron 18 , but seems the playwright get the firstWindow timeout,
my question is does latest playwright supported the electron 18 now???**
Issue Analytics
- State:
- Created a year ago
- Comments:19 (9 by maintainers)
Top Results From Across the Web
Common errors - FAQ - A progressive Node.js framework
Probably the most common error message is about Nest not being able to resolve dependencies of a provider. The error message usually looks...
Read more >Best Practices for Node.js Error-handling - Toptal
Developers working with Node.js sometimes find themselves writing not-so-clean code while handling all sorts of errors. This article will introduce you to ...
Read more >require() of ES modules is not supported when importing node ...
At the moment my .js file has nothing but the import of node-fetch and it gives me an error message. What am I...
Read more >Let It Crash: Best Practices for Handling Node.js Errors on ...
Before coming to Heroku, I did some consulting work as a Node.js ... When an error occurred, there was often not enough visibility...
Read more >TypeError: "x" is not a constructor - JavaScript - MDN Web Docs
The JavaScript exception "is not a constructor" occurs when there was an ... TypeError: Symbol is not a constructor function* f() {}; const...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That should be fixed in 1.28, please re-file if it still does not work!
Yes it does support Electron 18.
Could you provide us a minimal reproducible what exactly is not working so we can run it locally and find out if the Electron version is the root-cause of it?