search

mwittig / npm-license-crawler

Analyzes license information for multiple node.js modules (package.json files) as part of your software project.
BSD 3-Clause "New" or "Revised" License
234 stars 45 forks source link

“No such file or directory” Error #2

Closed swashcap closed 8 years ago

swashcap commented 8 years ago

Running npm-license-crawler . in a directory with a package.json and installed _nodemodules results in this error:

env: node\r: No such file or directory
uglow commented 8 years ago

+1 Same OS, NPM and Node. Using NVM, changed to Node v4.2.4, same result

mwittig commented 8 years ago

OK, I'll have a look at this asap.

mwittig commented 8 years ago

Guys, I think the problem is solved with the new release. The problem was the published command wrapper file contained CRLF line endings which causes problems specifically on OS X. Seems like a few other node projects had the same issue in the past. Originally, I developed on OS X, but I had to migrate my dev environment to Win 10, recently. On Windows, git will perform an autoconversion to CRLF by default on the local base - I wasn't aware of the consequences it has for OS X users. Sorry about that.

Please provide a short feedback. Thanks

mwittig commented 8 years ago

@swashcap and @uglow As you did not get back to me I assume the issue has been solved with the new release. May be the force with you!

uglow commented 8 years ago

Hi Marcus,

Sorry for not getting back to you. I used the parent dependency of this package instead, which met my needs at the time. If you reproduced the error, made changes and couldn't reproduce it anymore, then I agree that it's safe to close this.

Cheers, Brett

Sent from my iPhone

On 20 Jan 2016, at 9:12 PM, Marcus Wittig notifications@github.com wrote:

@swashcap and @uglow As you did not get back to me I assume the issue has been solved with the new release. May be the force with you!

— Reply to this email directly or view it on GitHub.

mwittig commented 8 years ago

Hi Brett,

Thanks for letting me know. If you only need to check licenses for a single package (which is the common case, I think) you'll be fine with license-checker.

Regards Marcus