Skip to content
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

Error create new project #17

Open
sebastienhouzet opened this issue Jun 8, 2020 · 7 comments
Open

Error create new project #17

sebastienhouzet opened this issue Jun 8, 2020 · 7 comments

Comments

@sebastienhouzet
Copy link

After install, i create new project

c4builder new

And i have this message:

_ _ _ _ _ _ ___| || | | |__ _ _(_) | __| | ___ _ __ / __| || |_| '_ \| | | | | |/ _ |/ _ \ '|
| (
|__ | |) | || | | | (| | / |
_
| || |./ _,|||_,|_|_|

Blow up your software documentation writing skills

This will create a new folder with the name of the project
? Project Name (node:42774) ExperimentalWarning: The fs.promises API is experimental
`

$ node -v
v10.15.1

@brugos
Copy link

brugos commented Jun 10, 2020

Similar error for me:

$ yarn global add c4builder
$ c4builder new
env: node\r: No such file or directory

node v12.16.3
[email protected]

@darrenmeehan
Copy link

I believe I also hit this issue, I worked around it by creating the directories manually first.

@damianesteban
Copy link

I believe I also hit this issue, I worked around it by creating the directories manually first.

What directories did you create manually? I'm still getting this error:

env: node\r: No such file or directory

after I create the directories.

@damianesteban
Copy link

I am on macOS and realized the issue was Windows line encodings. I pulled down the repo, installed dos2unix and ran the following command:

dos2unix **/*

Then I had to manually create the folders and it finally worked 😄 .

@erzz
Copy link

erzz commented Jun 16, 2022

A long time later - and this is still an issue?

➜ c4builder new
env: node\r: No such file or directory

Fresh installation - just wanted to try it out 😢

@adamclerk
Copy link

enabling autoclrf within the local git repository seems to resolve the issue when running the executable from the local repository on mac. fyi.

@mrevoir
Copy link

mrevoir commented Dec 21, 2022

Refer to #66

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants