on master help sign in
the file needs to be named elm.exe based on testing on Windows
64aa6f9Evan Czaplicki
installers/npm/bin/elm.cmd → installers/npm/bin/elm.exerenamed+6−1
@@ -13,7 +13,12 @@ var fs = require('fs');
13// the real binary over itself. So in that case, the first run would
13// the real binary over itself. So in that case, the first run would
14// also make an HTTPS request to fetch the real binary. From there,
14// also make an HTTPS request to fetch the real binary. From there,
15// it calls the binary it downloaded on each run.
15// it calls the binary it downloaded on each run.
16−
16+//
17+// It needs a .exe extension for Windows users. That file extension
18+// should allow this file to run both as a JS script and after it is
19+// replaced by the real Elm binary. The file extension does not appear
20+// to matter on Mac or Linux since it is hidden by the symlink at
21+// node_modules/.bin/elm that most people would refer to.
17
22
18
23
19// Make sure we get the right path even if we're executing from the symlinked
24// Make sure we get the right path even if we're executing from the symlinked
installers/npm/package.json+2−2
@@ -25,7 +25,7 @@
25 "install.js",
25 "install.js",
26 "download.js",
26 "download.js",
27 "bin",
27 "bin",
28− "bin/elm.cmd"
28+ "bin/elm.exe"
29 ],
29 ],
30 "keywords": [
30 "keywords": [
31 "bin",
31 "bin",
@@ -36,7 +36,7 @@
36 "installer"
36 "installer"
37 ],
37 ],
38 "bin": {
38 "bin": {
39− "elm": "bin/elm.cmd"
39+ "elm": "bin/elm.exe"
40 },
40 },
41 "dependencies": {
41 "dependencies": {
42 "request": "^2.88.0"
42 "request": "^2.88.0"