Angular CLI can't find modules from locally installed library.

[eestein]

Versions

Angular CLI: 1.7.4
Node: 7.7.3
OS: darwin x64
Angular: 5.1.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.7.4
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.4.2
webpack: 3.11.0

Repro steps

• create a library
• pack it using npm pack
• install the tgz file using npm install --save path_to_tgz_file
• run client project

Observed behavior

ERROR in ./src/app/app.module.ts
Module not found: Error: Can't resolve '@my_library/sdk' in '/Users/eestein/Documents/dev/my_library/sdk-front/samples/src/app'
ERROR in ./src/app/app.component.ts
Module not found: Error: Can't resolve '@my_library/sdk' in '/Users/eestein/Documents/dev/my_library/sdk-front/samples/src/app'

Desired behavior

Angular CLI would recognize the local package.

Mention any other details that might be useful (optional)

This is what I have in my package.json of the client project:

"@my_library/sdk": "file:///Users/eestein/Documents/dev/my_library/sdk-front/library/my_library-sdk-1.0.0-alpha.2.tgz",

If I open both offending files (app.component.ts and app.module.ts) in VSCode no error is shown. It looks like VSCode can find it, but Angular CLI can't.

This is my folder structure:

- library
   - library's code
   - *.tgz file
- samples
    - samples' code
    - package.json referencing the tgz file

[eestein]

Anyone?
I still can't fix it :/

Thanks!

[filipesilva]

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?

You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

[eestein]

@filipesilva Ok, I'm swamped with work right now, but I'll try to get it done by this Sunday/Monday.
Thank you for your support.

[eestein]

Hey @filipesilva, I've pushed the repro code here https://github.com/eestein/ng-extlib-bug-repro

I tried to remain pretty close to my real scenario. To run the project, use:

1 - Inside library folder: npm run build:local
2 - Inside samples folder: npm start

Please, let me know if you need anything else.

Thank you

[eestein]

@filipesilva hey man, any news on this? Could you reproduce? Thank you

[sporritt]

I have the same issue with one of my projects. Another problem I ran into was that I was unable to run the CLI 6 conversion utility (the project was originally in Angular 5) - the conversion utility failed to resolve the locally installed modules. Removing the locally installed modules from package.json allowed the conversion utility to run.

[sporritt]

i should point out that removing the node_modules directory and running npm install again made this issue go away for me.