Project not recognizing a newly generated package after npm install

[jbphillips]

Problem: "Cannot find module" after successful install of newly generated library

What I did:

• Using the yo angular2-library, I created a seed project
• I then built it , packed it, and published to myget/NPM
• I then npm installed generated project into a new Angular4 project
• I note that it is in node_modules
• Entering code in app.modules never resolves the path. i.e. "Cannot find module ... " import { SampleModule } from 'sample-library';

Any ideas why I might not find reference to my new generated library? Again, it is in node_modules as expected however while entering it into app.modules.ts, it cannot be found.

Thank you.

OS and Version?

Windows 7

Generator Version

11.4.0

Tools Version

Output from: yo --version, 2.0.0 Output from: node --version, 6.11.3 Output from: npm -v 5.3.0

Targeted Angular version

2+

Repro steps.

Install Yeoman: npm install -g yo Install Gulp: npm install -g gulp-cli Install Angular CLI: npm install -g

[tomwanzek]

I just migrated a Iocally developed library over to the latest version of the library generator. Here is what I noticed after the build process (dist folder)

• the package.json refers to ES-module entry points (module and jsnext:main) with the pattern {my-library-name}.js
• The actual entry point file generated by the build is however index.js

I suspect this disconnect is underlying this issue.

[tomwanzek]

An interim fix for me was to:

• update the module and jsnext:main entry points in the src directory package.json file to refer to index.js, and
• rebuild the distribution package.