Npm accidentally deletes packages installed via 'ng add'

Question

tested on node 13.10.1

I'm installing some Angular Libraries+schematics (written by me) via ng add command. The libraries are added to the package.json but not to the package-lock.json. When I try to serve my project, I got an error message for the libraries peerDependecies not satisfied.

I run npm i <missingpackages...>
I run ng serve

Then I got a new error, the Angular libraries I installed before are now vanished. Only their scope folder is left (@my-corp)

Then I re-run npm i <libraries...>,
ng-serve

And everything works fine (the libraries has been added to the package-lock.json too). Can anyone explains me this weird behaviour?

Do you find your libraries in your package.json? Maybe they're not there? — Ruben Szekér, Mar 11 '20 at 10:21
@RubenSzekér package.json is fine, with all the packages I added before — Nemus, Mar 11 '20 at 11:12
@Liam this issue is about npm/ng cli, how can I set an example? — Nemus, Mar 11 '20 at 14:40

score 0 · Accepted Answer · answered Mar 11 '20 at 16:25

I found a solution.

The core of the issue is the lack of updates in package-lock.json after the ng add <library>command was run.

If you're the angular-library developer, to solve this its sufficient to execute inside the rule factory function this code:

export function ngAdd(options: ISchema): Rule {
  exec('npm i --package-lock-only'); // <- this code
  return (host: Tree, context: SchematicContext) => {...};
}

If you're just a consumer, run this from the cli

npm i --package-lock-only

Hope this helps

Npm accidentally deletes packages installed via 'ng add'

1 Answers1