env: node\r: No such file or directory about basel HOT 10 CLOSED

So, i looked in to this...

Seems that in the distributed version on both MacOS and Linux there are non-unix line-endings being used in at least:

• bin/basel-crud.js
• bin/basel-database.js
• bin/basel-init.js

I forked the repo to fix it, but it turned out that the windows line endings where not present here.
This leads me to conclude that it must be an issue with the build tools that placed the package on npm.

Can you rebuild this package and push it to npm again?
This version has been online on npm for a year now and it affects 2 of the 3 available platforms which is quite a huge part of your audience.

from basel.

@acidfilez thanks for your fix!

from basel.

Great!

Can You help to fix it in installation?

from basel.

Getting the same message "env: node\r: No such file or directory" tried @acidfilez fix to no avail. Returns all "Can't open : No such file or directory".

I am running a new build of Sierra 10.12.5
Fresh install of node v6.10.3

Thanks.

from basel.

@acidfilez work for me on mac 👍

from basel.

issue confirmed on Ubuntu

from basel.

Hi @woutervddn
Did you submit a Pull Request?

from basel.

Try to read my post again, the code in this repo is fine.

During the checkout to your build system the windows line endings where appended. This is due to your personal git configuration on Windows. The npm package that got build and published from there contained the these CR + LF endings where Linux and MacOS only work using LF.

DOS uses carriage return and line feed ("\r\n") as a line ending, which Unix uses just line feed ("\n").
In order to make this work the project own on npm must change his personal git configuration, rebuild and republish to npm

More information about this can be found here:
https://en.wikipedia.org/wiki/Newline

from basel.

Just had the same problem on Ubuntu?

Have you guys found a way to fix it?

from basel.

Finally fixed:
sudo npm install -g github:baseljs/basel#v0.1.2

from basel.