-
-
Notifications
You must be signed in to change notification settings - Fork 746
Core: Introduce cross-platform npm restore and check mismatch on publish #988
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Core: Introduce cross-platform npm restore and check mismatch on publish #988
Conversation
pr-comment: Run #2
🎉 All tests passed!Github Test Reporter by CTRF 💚 🔄 This comment has been updated |
c4f8292 to
9d03787
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 8 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs
Show resolved
Hide resolved
src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs
Show resolved
Hide resolved
src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs
Show resolved
Hide resolved
src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs
Show resolved
Hide resolved
FlorianRappl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great one !
I need a package 😍 |
This PR may seem contradictive at first sight.. :-)
It does this:
This has caused user confusion because it can too easily be gotten wrong. Now it's no longer possible to build for OS A on OS B.
One exception: Linux packages can be build on Windows (WSL)
npm installThis means for example: When you are on Windows and osx-x64 is selected as RID, then the npm restore will do the restore as if it was on OSX.
In case of mismatch, it exists with an appropriate error message
(it would fail anyway, but without explanation otherwise)
So - why do x-platform npm restore first and then error out on platform mismatch when publishing?
It's all about debugging - remote debugging. And again, the fast way is of course without packaging - i.e. how debug is working now. For remote debugging, we need to have everything ready to work on the target/remote machine. For .net it's not a problem anyway, but the Electron executable is platform-dependent, This PR allows to get the right one, so that we can end up with a file set which runs on the target direct.ly, without any additional steps needed.