[npm]: "WARN reify invalid or damaged lockfile detected"

[jnoga]

Hi!

I've been using this package for a while, and it seems that something is wrong with the package-lock file since Node 16.15.1 version (NPM 8.5.5). When installing the package with, at least, that version of NPM I get this message:

npm WARN reify invalid or damaged lockfile detected
npm WARN reify please re-try this operation once it completes
npm WARN reify so that the damage can be corrected, or perform
npm WARN reify a fresh install with no lockfile if the problem persists.

And after this if I try no make a clean install with npm ci I get a fatal error:

npm ERR! code EUSAGE
npm ERR! 
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm ERR! 
npm ERR! Missing: @linthtml/linthtml@ from lock file
npm ERR!

Steps to reproduce the bug

Before trying to reproduce the bug please make sure you have, at least, the 16.5.1 version of NodeJS installed.

1. Create an empty folder, init npm there with npm init and change move there.
2. Install the package npm i --save-dev @linthtml/linthtml
3. Try to make a clean install with npm ci

Environments

I have reproduced the bug in MacOS and Debian environments.

Any clue to resolve this issue will be really appreciated, thanks in advance

[KamiKillertO]

@jnoga Thanks for reporting, I'll have a look

[jnoga]

Just an appointment, it seems that the reason of the error are these deleted lines in the package-lock file:

"@linthtml/linthtml": {
"dev": true,
"peer": true
},

and

"node_modules/@linthtml/linthtml/node_modules/@linthtml/linthtml": {
"dev": true,
"peer": true
},

Hope it helps

[KamiKillertO]

Sorry for the late answer.
Looks like the problem is caused by the fact that @linthtml/linthtml is a peer deps of @linthtml/cli and that @linthtml/cli is a dep of @linthtml/linthtml.
Looks like I missed something when I made the split in monorepo.

I have a fix ready. I am going to released it as soon as possible

[KamiKillertO]

@jnoga I have just release a new version that fix fix issue

[jnoga]

Thank you very much! I will test It as soon as possible to clóse the issue

[jnoga]

Closing, thanks again!