-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Cannot build on Windows due to Bash usage #4720
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
Comments
@timfish - Can you say more about what actually goes wrong? What about the script is it unhappy with? |
Windows does not have bash so the script completely fails to run. I suppose WSL might work but this was never a requirement before and it's a huge dependency. |
Forgive my ignorance, but really? I feel like shell scripts are all over the place in software development. Can folks who use windows machines truly not run any of them (without WSL, at least, which is sounds like isn't a part of your normal setup or an everyday thing)? What do you do instead? There are other bash scripts in the repo. How do you run them? |
Yup, you need a WSL (now) or Cygwin, MinGW or msys (old days) 🥲 |
This also applies to |
Shell scripts may be common in some areas of software development but they are rare in the node.js ecosystem. JavaScript projects stick to package.json scripts and node.js scripts to retain cross platform compatibility and to reduce barriers to outside contribution. For things like Relay where there are few outside contributions, Windows support doesn't really matter but for a repository like this there should be a policy over whether to stick to solely node.js or not.
When issues pop up in the build or unit tests I submit PR's to fix them! Currently, I just let the integration tests run in CI. |
Oh, and I'm happy to do a PR to remove shell script usage if that's direction we want to go! |
Wow, well - TIL. (I think you're literally the only person I know who works on a windows machine, LOL.) We chatted about it at our standup, and we're good to move to only node scripting going forward (probably everywhere, but at least for build for sure). And thanks for the offer to help! The bash scripts that @Lms24 and I have introduced over the last week or two it's probably just as easy for us to convert since they're fresh in our minds, but if there are others that need fixing, by all means - we'd be glad for the assistance! Coincidentally, I actually just merged a PR adding |
I've mainly worked on desktop software so need at least one device per platform. I've even got a cheapo laptop that was emergency purchased specifically to tune and test multi-touch touchscreen interactions. I spend the majority of my time and travel with whichever device is newest/fastest and that's currently Windows. I'd guess by the end of the year I'll have a new Mac and that will become the default 😂 Drop me a message here if you've got any scripts you want me to tackle! |
@timfish so is this something you are comfortable taking on? only thing to note, is that these are some scripts which have been recently added and @lobsterkatie or @Lms24 would like to change them themselves
|
Yes I'll take this on. I'll leave the above mentioned files for now! |
Both |
I'm actually in the middle of revamping |
@timfish I was planning on working on |
Because SDK developers running Windows [can't run our bash scripts[1], we recently decided to move to using TypeScript instead. To make this easier, this extends the domain of our `eslint` and `prettier` checks to include all `scripts` folders. It also fixes a few linting errors which doing so brought to light. [1] #4720
Is there an existing issue for this?
SDK Version
master
Steps to Reproduce
yarn && yarn build
Expected Result
Builds
Actual Result
Fails on
bash scripts/buildBundles.sh
The text was updated successfully, but these errors were encountered: