-
Notifications
You must be signed in to change notification settings - Fork 23
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
Paths on Windows #1
Comments
Hey dothem1337, sorry I didn't see this issue earlier in the weekend. If you've already created a solution, I'd love to review a PR. Otherwise, if you can give me a couple days to figure it out, I might be able to resolve this one myself. I really only have experience with linux/Mac, so any tips or experience you can share would also be helpful to get this feature/fix out quickly. Thanks! |
Just doing some cursory reading, and now I'm curious where specifically you are getting errors? |
hey @tehpsalmist The problem is on build, so on npm start or something else, it will fail, because it cant not resolve the ./node_modules/.bin path. Windows cant handle ./ paths. I fixed it with the follwowing: path.resolve
But now, I have another problem with the watch. It doesnt watch my files. And I did not found out why. The changes to the files take no effect and will not be rebuilded. |
Ok, it sounds like Windows is going to have many issues with this path problem. I'm not sure how soon I'll be able to roll out a solution, or how well tested it can be, since my only windows machine is in parts right now. I'll figure something out. In the meantime, if you want to submit a PR, that would be helpful too. Thanks for all the feedback! |
@dothem1337 , I think I have some solutions in the works here. Stay tuned for a release, and if you can reproduce the watch error, and let me know what your |
hey, great lib!
But i have problems on windows system with the build process. Windows does not like ./ paths. Can you maybe fix this? :)
If not, I can build my own lib for windows :)
Thank you!
The text was updated successfully, but these errors were encountered: