npm run build wrong, Could you kindly update package.json?

[alethio]

npm run build wrong, Could you kindly update package.json?

[use-strict]

As far as I can tell, the problem comes from using yarn instead of npm. Yarn needs its own yarn.lock file which is not compatible with package-lock.json. If you intend to use yarn, you can try to run yarn import to convert the lock file in your local checkout (https://yarnpkg.com/lang/en/docs/cli/import/). Please note, however, that we don't officially support yarn and that our packages are built and tested against latest LTS node/npm.

I recommend following the steps in the readme, doing an npm install followed by npm run build. This should avoid similar problems in the future.

[willzhuang]

npm was resulted the same problem in verison of 8, 10, and 11.
I changed in package.json, "ethstats-ui": "^1.0.0-beta.3" to "1.0.0-beta.3"，both npm and yarn are OK.

[use-strict]

That's weird. It should use package-lock.json regardless of whether you use a fixed version in package.json or a caret (^). You could try to delete the node_modules folder. npm tends to prefer what you already have installed there. Either way, we are close to releasing a new version of the lite explorer, which uses updated dependencies.