-
Notifications
You must be signed in to change notification settings - Fork 2.1k
fix: adjust binary call for microfrontends proxy on Windows #10962
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
fix: adjust binary call for microfrontends proxy on Windows #10962
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Thanks, @mknichel! Tried out the original proposal and it broke macOS, so I'm going to try a slightly different approach that only changes the semantics of the binary call on Windows. Let's see how that does. |
|
The Windows failure seen in CI is not related to this branch. It can be observed on other branches as well. Merging past the failure; we will fix in another PR. |
Description
The microfrontends local development proxy fails to start on Windows because it runs into:
%1 is not a valid Win32 application. The issue is that Turborepo runs the.jsscript and relies on the shebang to be run correctly. That doesn't work on Windows. This PR changes the code to runnodewhich will work on Windows.Testing Instructions
In a microfrontends repository, such as https://github.com/vercel-labs/microfrontends-nextjs-app-multi-zone, run
pnpm turbo run devon Windows and ensure that it starts up.