-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
preact create exits with status 1 #415
Comments
After upgrading yarn to v1.2.1 the same bug remains |
I think #409 might fix this issue. |
No, I don't think so, the name in package.json is correct and I think it's a WSL/YARN realated issue. The only reason it might not be is because it worked before on Preact CLI v1.4 |
Not sure if this is related, but I tried to create/install with:
And the "name" field in package.json was, literally There was no log file, just |
Yeah, that's another issue. For now add the --name flag to the Preact create command and the name is correct in package.json :) |
Hi, I have the same issue right now with:
The
{
"private": true,
"name": "new-project",
"version": "0.0.0",
"license": "MIT",
"scripts": {
"start": "if-env NODE_ENV=production && npm run -s serve || npm run -s dev",
"build": "preact build",
"serve": "preact build && preact serve",
"dev": "preact watch",
"lint": "eslint src"
},
"eslintConfig": {
"extends": "eslint-config-synacor"
},
"eslintIgnore": [
"build/*"
],
"devDependencies": {
"eslint": "^4.5.0",
"eslint-config-synacor": "^1.1.0",
"if-env": "^1.0.0",
"preact-cli": "^2.0.0"
},
"dependencies": {
"preact": "^8.2.1",
"preact-compat": "^3.17.0",
"preact-router": "^2.5.5"
}
} As well as a README.md and a src folder. If I do a I'm a beginner with preact and preact-cli, I'm maybe missing something. |
@Dylanderv are you using the latest version of CLI? |
@m4r1vs this is fixed in |
@reznord Yes, I'm using |
@Dylanderv ummm....I just checked it in my machine and it was working fine for me. Can you please give me the steps to reproduce this? |
I'm not doing anything more than I'm using node v8.4.0 and npm 5.3.0 with nvm on Debian stretch. |
@Dylanderv are you using Sinopia/Verdaccio by any chance? |
Can't reproduce this in the latest version of CLI (closing for now). Feel free to re-open if anyone still faces the same issue. |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
when creating a new PWA with following command:
preact create default --name caf-menu --git --force --yarn
I get this output:
⚠ WARN Insufficient command arguments! Prompting...
ℹ INFO Alternatively, run preact create --help for usage info.
? Directory to create the app caf-menu
? Install dependencies Yes
ℹ INFO Assuming you meant preactjs-templates/default...
⠙ Installing dependenciesError: Exited with status 1
And the created folder-structure looks like this:
caf-menu
yarn-error.log looks like this:
If the current behavior is a bug, please provide the steps to reproduce.
See above
What is the expected behavior?
That the command doesn't exit with an error and works like it did on preact-cli version 1.4
Please mention other relevant information.
The text was updated successfully, but these errors were encountered: