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

Open
dmitriid opened this Issue Mar 31, 2016 · 1 comment

Projects

None yet

3 participants

@dmitriid

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
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment