-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Getting starting guide is missing a comma #1280
Comments
The example is correct. It is up to you to add the correct amount of commas to your package.json. We cannot know what your package.json looks like and if you add the "scripts" section as last item to your package.json, you will not be needing to add a comma. If you add it anywhere in between, you will. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
There is a missing comma at the end of line 48 in
README.md
, in the getting started guide. If you add the comma to thepackages.json
, you will have yournpm test
run. Sorry can't produce a test case, but here is a screenshot of what happens:The first one was without a
package.json
, second one was with a touched one, but with nonpm init
having been run. Is this an issue?Here's what it looks like with the comma:
The text was updated successfully, but these errors were encountered: