-
Notifications
You must be signed in to change notification settings - Fork 108
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
Update repo docs to add instructions for windows WSL mode #106
Comments
you need to set up and run things in WSL when using windows will leave this issue open to update the docs |
I have this set-up, already to allowe run I perceived it instead as though you were setting up for installing I will see the video again sometime, but for now I will just stick to my workaround. ✌🏾 |
the video is comprehensive, covering everything your fix wouldnt work on max/linux and so cant be commited WSL is "linux in windows" and gives the best experience for all contributors |
Haha 😃, ofcourse... That's why its "my workaround". |
dev
scripts not compactible with window machine
Local dev dosnt work directly on a windows machine
Windows users should instead set up and use WSL
@McPizza0 created a lengthy guide to set thing up as a video: https://www.youtube.com/watch?v=xL-nwGpQ0Ng
we need to summarize this into steps and potentially add it to a linked doc from the main readme
Original issue:
I ran into this while tryna set-up my local dev server on my windows machine.
Windows users encounter errors running scripts due to differences in command syntax. I think the scripts across all apps have been written in a ways that isn't exactly cross-compactible, the current script look like they run only on
Unix-based systems
(I think 😬).Steps to Reproduce:
pnpm run dev
Expected Behavior:
Scripts should run without errors on Windows.
Actual Behavior:
Windows throws an error because it does not recognize the syntax
PORT
. Notice the specific error in the log below...Workaround:
Modify the
dev
scripts in allapps
package.json using the format below in places wherePORT
are setReplace
3***
with appropriately stated port and replace<command>
with the already existing commandProposed Solution:
Update all scripts in the repository to use cross-platform compatible syntax.
Additional Notes:
The text was updated successfully, but these errors were encountered: