Running into an error with npm install

[alecnicolas]

Using https://developer.okta.com/blog/2019/05/13/angular-8-spring-boot-2 to set up Okta on an Angular and Spring app.

Upon running ng add @oktadev/schematics:

ENOENT: no such file or directory, open './package-lock.json'

[frlzjosh]

I get the same issue when runningng add @oktadev/schematics as well as with yarn. The error is always ends up being:

npx npm-force-resolutions
Arguments:
Directory: <app-folder-directory>/@oktadev/schematics
Output:

[mraible]

If you run "npm install" first, does it work?

…

On Dec 14, 2019, at 20:28, Joshua Magdaleno ***@***.***> wrote:  I get the same issue when doing ng add @oktadev/schematics as well as with yarn. The error is always ends up being: npx npm-force-resolutions Arguments: Directory: ***@***.***/schematics Output: — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[mraible]

Thanks for reporting this issue. Fixing now...

[mraible]

Should be fixed now.

[bertyhell]

For future reference this was fixed by removing the npx npm-force-resolutions command from package json:
1d228f3