-
Notifications
You must be signed in to change notification settings - Fork 45
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 npm install
on Windows OS
#491
Comments
Sorry. |
So I am trying to experiment over the fresh 1d51383 state...
The
|
So, it looks like
When I replace the environment variable with
I am able to run |
I think, there are two possible ways to overcome this issue:
|
And here you are mliebelt/chessground#1 (I think, if the PR will be accepted (please, try it) then this issue can be closed.) |
Ok, I have merged your pull request. I tried some months ago to upgrade Chessground to the newest version, but failed, and did not find out the reason for that. Perhaps I will try that again, to get rid of the necessity to build Chessground on my own. For the moment, you should be able to build pgn-viewer again. |
It was first thing I tried too. Also failed.
I was able to do so using my own build, forking yours, so I expect it really should work now. Thank you 👍 |
It is a fresh problem.
After 1d51383 the
npm install
ends with errors, while when checkouting the previous commit 8682404 it works without any error.The
C:\WINDOWS\system32\cmd.exe /d /s /c $npm_execpath run compile
cannot work on Windows OS, as there should be%npm_execpath%
or something, and also this environment variable set. Maybe thepackage.json
contains more than necessary?The text was updated successfully, but these errors were encountered: