Skip to content
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

Unable to install ephemeris on windows using either of npm or yarn #12

Open
gentlesammy opened this issue Oct 5, 2020 · 4 comments
Open

Comments

@gentlesammy
Copy link

ephemerisissue
Please help make this awesome package to work on windows. I have tried all means to install it but i keep getting error. I used both yarn and npm but i keep getting the same error as can be seen in the screenshot

@stenflo
Copy link
Collaborator

stenflo commented Oct 22, 2020

Hi @gentlesammy - thanks for reporting this issue. I can see what the issue is and will keep this bug open until we provide a fix in the near future. The problem is that the string "scripts/build.js" in our postinstall script is hardcoded to use a forward slash and windows needs it to be a backslash. Until we fix this you might be able to work around it on your windows machine by using powershell or cygwin (I haven't tested it with these but presume they will allow it to work). If you can successfully get past the install/postinstall script with powershell or cygwin then you can return to the default command prompt. Hope that helps!

@stenflo stenflo mentioned this issue Nov 23, 2020
@GrayYoung
Copy link

I have the same issue. Using PowerShell or cmd to install the package failed either.

@stenflo
Copy link
Collaborator

stenflo commented Sep 30, 2022

Hi GrayYoung - I believe this issue has been resolved in the current master branch already. It was resolved with a commit dated 11/23/2020 when gulp was introduced to the project. However, no new versions have been cut since this fix was integrated to the master branch, so the version 2.0 (latest) release in the npm registry does not include this fix. Therefore, I suggest you could pull the latest revision of master branch if you need this fix, or otherwise wait patiently for the next release.

@GrayYoung
Copy link

@stenflo Thanks, it did work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants