-
-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Full Windows support #7
Comments
Sure, I'll try all the commands & scripts from scratch when I get some time and report back. I'm your worst case user - using npm2 on Windows, running on the cheapest Lenovo laptop Amazon UK had 5 months ago, with a crap CPU and an HDD 😸 Anything which uses vanilla Babel 6 presets is pretty miserable to install on npm2 with this setup due to the duplicated dependencies for each plugin. |
Yeah.. I wonder if we can do something crazy like put all non-binary deps in a tarball or something. |
Until the packages are public, you can do this to test the full flow: npm i -g counter-redux@qwertyuiop
create-react-app whatever --scripts-version react-elmish-example@bundled |
Interesting.
to see if |
Ah I see |
Eh, that’s not fun. Maybe I could exclude whatever depends on |
A little nitpick: the message for
because |
Yeah, I was hoping that maybe people would just read it as a word if they know there is no such command. Open to better ideas (can check platform?) |
OK I can't find any more ways to break it. So just two big things, |
For the build message, you could check for Windows doesn't ship with a Python installation, though - a handy alternative would be to recommend |
Do you have an AppVeyor account to run CI on Windows? Better to have things checked automatically on all platforms, but new tests would need to be written. |
I think we’re good. I’ll double check now. |
Okay, final prerelease: npm i -g counter-redux@qwertyuiop
create-react-app my-app --scripts-version react-elmish-example@pretty-close |
Remove non-text character from tsconfig.json closes #5
Also when installing, if it throws a "JSON" error and crashes, try running this command: create-react-app appname --save or create-react-app appname --save-exact and then try again. if it persists you can try using a newer version of node. |
I believe @insin has access to Windows—would be great if we could keep track of things that are still broken/missing there. Let’s close this issue when the support is complete.
@insin Can I ask you to write up a checklist if there’s more than a few broken things so we keep track of them?
TODO:
The text was updated successfully, but these errors were encountered: