Skip to content
This repository has been archived by the owner. It is now read-only.

Failing to parse package.json must be an error, not warning #12155

Closed
dmitriid opened this issue Mar 31, 2016 · 2 comments
Closed

Failing to parse package.json must be an error, not warning #12155

dmitriid opened this issue Mar 31, 2016 · 2 comments

Comments

@dmitriid
Copy link

@dmitriid dmitriid commented Mar 31, 2016

Given

{
  'name': 'some-name',
  'dependencies': {}
}

Running

> npm --version
3.3.12

> npm install --progress=false --loglevel=error
> 

> npm install
npm WARN EJSONPARSE Failed to parse json
npm WARN EJSONPARSE Unexpected token '\'' at 2:3
npm WARN EJSONPARSE   'name': 'some-name',
npm WARN EJSONPARSE   ^
npm WARN EPACKAGEJSON campaign No description
npm WARN EPACKAGEJSON campaign No repository field.
npm WARN EPACKAGEJSON campaign No README data
npm WARN EPACKAGEJSON campaign No license field.

Failure to parse package.json must be a fatal error, not a warning

@lholmquist
Copy link
Contributor

@lholmquist lholmquist commented Sep 8, 2016

@dmitriid @othiym23 should this be closed? looks like it was fixed here: #12406

@npm-robot
Copy link

@npm-robot npm-robot commented Jun 19, 2017

We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.

If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

@npm-robot npm-robot closed this Jun 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants