Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Package.json incorrectly formatted

See original GitHub issue

I’m getting a failure on a Travis build from this update. Looks like you just added a dual-module package. With type: module in the package.json, I think main should point to the ESM build or needs the .cjs extension.

Build is here: https://travis-ci.org/github/mAAdhaTTah/brookjs/jobs/679426871

I haven’t written a dual module package, so I could be wrong on the fix, but the current implementation is def broken, unfortunately.

Issue Analytics

State:
Created 3 years ago
Reactions:22
Comments:6 (2 by maintainers)

Top GitHub Comments

4reactions

nprailcommented, Apr 25, 2020

This issue breaks @angular/cli as well.

Solved it by pinning the version in the package-lock.json file like so:

"is-promise": {
  "version": "2.1.0",
  "resolved": "https://registry.npmjs.org/is-promise/-/is-promise-2.1.0.tgz",
  "integrity": "sha1-eaKp7OfwlugPNtKy87wWwf9L8/o=",
  "dev": true
}

1reaction

evicentcommented, Apr 25, 2020

#12 solution here!

npm remove is-promise npm install is-promise@2.1.0

Try and let your comments