-
Notifications
You must be signed in to change notification settings - Fork 184
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
Cannot start server on Windows #534
Comments
@kimgronqvist I would love to get react server up and building on windows, but I don't have a machine to debug on. We hit some errors trying to set up appveyor to prevent these kinds of compatibility issues from sneaking in. Would you be willing to help us get the build passing on windows? |
Sure! On what command is the build failing? I've tried running |
Yay! 🎉 I opened up a pr to add appveyor to the build in my fork, since I'm not sure how to set it up so that it only builds for a single branch and not for a whole repo. You can see the full logs here, or by following the link in the failing check, but currently its failing
I don't really understand why that would be the case, though, since its passing our ubuntu build just fine. The dev dependency we've declared should be added by npm to the path at runtime. |
Also, the issue is #316 |
@doug-wade - Looks like there were some build failures higher up. Maybe mocha (or one of its deps) just failed to build? |
Related, in react-server-cli/target/compileClient.js there's a few calls to require.resolve where the result is used in a string output. For example, require.resolve("react-server-core-middleware"); |
When writing
routes_client.js
on Windows, you currently output require-statements with single backslashes - which doesn't work.A small change to
compileClient.js
(308) is needed. There's problaby a nicer solution, but this fixed it for me.The text was updated successfully, but these errors were encountered: