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.

The `main` field in package.json points to the wrong file.

See original GitHub issue

Inside the package published to npm, the main field in package.json points to the wrong file. It is probably caused by an error in the last publish and not using lerna as it shuled

Closes: #571 Closes: #573 Closes: #574 Closes: #576

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:16

Top GitHub Comments

5reactions

vanhoutenboscommented, Jan 22, 2020

Hi daniel,

Thank you for noticing this, i will get right on it!

3reactions

nikandlvcommented, Jan 26, 2020

@jeanpoelie 0.13.6 broke because you updated the dom-helpers and that file its trying to compile that properties file which does not exist on last version of dom-helpers, second issue is even if you manually downgrade the dom-helpers, it compiles however it breaks change of pages

Top Results From Across the Web

Main property in package.json defines package entry point

It will be used to point a file inside the package directory that will be the entry point. If main property does not...

How to use the 'main' parameter in package.json?

The main field is a module ID that is the primary entry point to your program. That is, if your package is named...

package.json - npm Docs

The main field is a module ID that is the primary entry point to your program. That is, if your package is named...

API - esbuild

There are two main API calls in esbuild's API: transform and build. ... This changes how the exports field in package.json files is...

What Is package.json? | heynode.com

"main": "src/index.js",. The main field is a functional property of your package.json. This defines the entry point into your project, and commonly ...