jspm-cli: Trailing CR causes jspm to fail on Unix

JSPM Version: beta.46

Transpiler Plugin(s): I do not use a transpiler

Details: It appears that some bad carriage return characters got their way into jspm.js. It just started happening with the new beta.

The consequence is that beta.46 introduces issues on both Mac OS X and Linux, where the following issues shows up:

$ ./node_modules/.bin/jspm 
env: node\r: No such file or directory

The \r hints at some carriage return stuff. It is confirmed by running diff on jspm.js on the beta-45 and beta-46 with and without the strip-trailing-cr option:

$ diff --strip-trailing-cr /tmp/v45/node_modules/.bin/jspm /tmp/v46/node_modules/.bin/jspm | wc -l
       0
$ diff /tmp/v45/node_modules/.bin/jspm /tmp/v46/node_modules/.bin/jspm | wc -l
      88

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 15 (8 by maintainers)

Most upvoted comments

I’ve published a 0.17.0-beta.47 to resolve this. It’s very odd that a standard NodeJS publish workflow doesn’t work in Windows due to this convention breaking. Shows how unix the culture is!

guybedford on Oct 20, 2017