-
Notifications
You must be signed in to change notification settings - Fork 667
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
Remove system-specific carriage returns #564
Comments
Been talking with @rachelnabors, it looks like this happens with any command in the CLI. |
`#!/usr/bin/env node` was causing sonar to throw `env: node\r: No such file or directory` from the command line on my Mac. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Ref webhintio#564 Fix webhintio#564 Close webhintio#564
`#!/usr/bin/env node` was causing sonar to throw `env: node\r: No such file or directory` from the command line under some configurations. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Fix webhintio#564
`#!/usr/bin/env node` was causing sonar to throw `env: node\r: No such file or directory` from the command line under some configurations. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Fix #564
The problem is not with
From https://docs.npmjs.com/files/package.json#bin
Note: I've reverted #564, as otherwise, something similar to this will happen for users when trying to execute /Users/alrra/.nvm/versions/node/v8.1.3/bin/sonar: line 1: use strict: command not found
/Users/alrra/.nvm/versions/node/v8.1.3/bin/sonar: line 2: syntax error near unexpected token `exports,'
/Users/alrra/.nvm/versions/node/v8.1.3/bin/sonar: line 2: `Object.defineProperty(exports, "__esModule", { value: true });'
The problem is that, for some reason, on @rachelnabors' system there is a
I don't see any carriage return in the code, nor the generated code from |
@molant The problem is that when you did the release, since you did it from Windows, when the build process was executed it automatically inserted the |
I published a new release that should fix this issue. @rachelnabors Can you reinstall |
From https://www.typescriptlang.org/docs/handbook/compiler-options.html: " --newLine Use the specified end of line sequence to be used when emitting files: 'crlf' (windows) or 'lf' (unix). " - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Fix #564
From https://www.typescriptlang.org/docs/handbook/compiler-options.html: " --newLine Use the specified end of line sequence to be used when emitting files: 'crlf' (windows) or 'lf' (unix). " - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Fix #564
From https://www.typescriptlang.org/docs/handbook/compiler-options.html: " --newLine Use the specified end of line sequence to be used when emitting files: 'crlf' (windows) or 'lf' (unix). " - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Fix #564
Looks like there's a Window's specific carriage return goofing things up on my Mac:
Environment
Mac, running NVM. Am unable to create
.sonarrc
.Node.js
version: v8.6.0npm
version: 5.3.0The text was updated successfully, but these errors were encountered: