-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Unable to build under windows - error at test:bin task #1233
Comments
I don't have a windows box to test on, but if you submit a PR that fixes that issue, glad to accept. |
Test with AppVeyor CI. This should get it going quickly and easily: https://github.com/stevenvachon/hidefile/blob/master/appveyor.yml |
Done in #1244 There still a issue with istanbul i could not find how to fix |
#1346 should fix this |
Edit: sorry i think that was already merged. will try the PR Hi updated and still getting an error:
There's a I change to call
Since fork is for a node.js module i tried spawn also without luck Using node 6.9.1, windows 10 |
Have you tried what you wrote and then notice that the PR was not merged yet? Or did the PR-commit not work either? I have merged the PR now, so maybe you could try again. |
The mentioned issues were before merging. I tried the PR but got eslint errors. Will try after the merge |
I manually applied the changes to master branch and worked fine. I can do a PR if necessary. The 4.x build failed with an error in jison but this is another issue |
I thought I pushed the merge to master already. No need to do a PR. I regularly merge from 4.x to master.
Is the jison error related to line endings? May there need to be more entries in .gitattributes
Am 14. Mai 2017 17:41:16 MESZ schrieb "Luiz Américo" <notifications@github.com>:
…I manually applied the changes to master branch and worked fine. I can
do a PR if necessary.
The 4.x build failed with an error in jison but this is another issue
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#1233 (comment)
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
|
I don't know. There was an error previously i don't remember exactly:
|
@blikblum After changing the eol of handlebars.I to unix it worked. (That is what you found out about a year ago. A year can be a very long time, I know that.) I have added a .gitattributes-entry to fix that on Windows. Deletion and `git reset --hard' may be necessary to apply the changed line-endings. |
Fixes handlebars-lang#1233 NodeJS files cannot be executed directly on Windows.
About the original issue: It still exists, but I'll integrate your suggestion, maybe slightly different, because on Linux it would still be good to call the script without the "node "-prefix |
I have update branch issue-1233, wihch has "appveyor.com" configured as CI-service. I would be cool if someone could look into that. |
Closes #1233 - Handle path-separators properly. Use "path.sep" instead of "/". Or use "require.resolve()" if possible - Use "execFile" instead of "exec" to run the Handlebars executable. This prevents problems due to (missing) shell escaping. - Use explicit call to "node" in order to run the executable on Windows. - Add "appveyor"-CI in order to run regular tests on Windows.
Released in 4.0.11 |
Cloned handlebars.js repository under windows 10 64bit, node 4.2.1
Installed dependencies
npm install
Ran
grunt
. Initially there was an error in jison. After changing the eol of handlebars.I to unix it worked.Again ran
grunt
Got the following error:
Running "test:bin" task
Fatal error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "./bin/handlebars -a spec/artifacts/empty.handlebars"
To run ./bin/handlebars file under windows is necessary to execute
node ./bin/handlebars
The text was updated successfully, but these errors were encountered: