Any updates?

Any update here?

Importing it from where it is defined is work for me.

It is a problem for me as well, with @angular/cli 7.2.6 & @angular/cli 7.3.3. Is there any plan to fix this?

I noticed unexpected (for me) behavior:

//== Class that use interface from barrel-file
import { IBodyInterface } from '../interfaces'; // => Import from barrel

export class MyModel {
  public Body: IBodyInterface;
}

//== Barrel
export { IBodyInterface } from './body.interface';

In this case i got error TypeError: Cannot read property 'module' of undefined. But if edit export string in barrel file to export * from './body.interface'; build error will disappear

Is there any workaround ?

The issue https://github.com/ng-packagr/ng-packagr/issues/1173#issuecomment-551577679 referred me to this issue.

This issue prevents my library to use secondary-entry points and would save a lot of package size because of non-tree-shakable third-party libs. Neither is Ivy a thing for library-authors yet nor is there a workaround for this issue (at least I could not get it working)

How can this be a very low priority issue?

If this is not related to this issue I can open a new issue instead.

Addition to this issue

I tried to create two secondary entry points. One does work, one does not and I can’t see a difference.

This does work

ui/charts/package.json

{
  "ngPackage": {
    "lib": {
      "entryFile": "../src/lib/components/data/chart/public_api.ts",
      "umdModuleIds": {
        "chart.js": "chart.js"
      }
    }
  },
  "peerDependencies": {
    "chart.js": "^2.8.0"
  }
}

public_api.ts

export { ChartModule } from './nx-chart.module';
export { ChartBarComponent } from './chart-bar/chart-bar.component';
export { ChartLineComponent } from './chart-line/chart-line.component';

This does not work

ui/object-editor/package.json

{
  "ngPackage": {
    "lib": {
      "entryFile": "../src/lib/components/inputs/object-editor/public_api.ts",
      "umdModuleIds": {
        "ang-jsoneditor": "ang-jsoneditor",
        "jsoneditor": "jsoneditor"
      }
    }
  },
  "peerDependencies": {
    "ang-jsoneditor": "^1.9.0",
    "jsoneditor": "^8.0.0"
  }
}

public_api.ts

export { ObjectEditorModule } from './object-editor.module';
export { ObjectEditorComponent } from './object-editor.component';
export { ObjectEditorSectionComponent } from './object-editor-section/object-editor-section.component';

Error message

------------------------------------------------------------------------------
Building entry point 'ui/object-editor'
------------------------------------------------------------------------------
× Compiling TypeScript sources through NGC
ERROR: Cannot read property 'module' of undefined
An unhandled exception occurred: Cannot read property 'module' of undefined
See "..." for further details.

Further information

@angular-devkit/architect          0.1100.5
@angular-devkit/build-angular      0.1100.5
@angular-devkit/build-ng-packagr   0.1001.4
@angular-devkit/core               11.0.5
@angular-devkit/schematics         11.0.5
@angular/cdk                       11.0.3
@angular/flex-layout               11.0.0-beta.33
@schematics/angular                11.0.5
@schematics/update                 0.1100.5
ng-packagr                         11.0.3
rxjs                               6.6.2
typescript                         4.0.3

Conclusion

The only difference I spot is the dependencies of both entry points. I’d be happy to help with further information if you need them.

Instead of index.ts files,

import { SomeComponent, SomeService } from '../something';

we’re using private Angular Modules

import { SomeModule } from '../something.module';

This helps in a few cases to reduce direct referencing.

But index.ts files would be much better!!!

Any ETA on this ? Resolving from index barrel is kind of important on large, multi-teams project…

For Angular Library make sure your index barrel are exported in your library main index barrel (aka public_api)

I was getting this error in my angular library when I imported like:

import { thing } from 'directory';

But this workaround fixed it for me:

import { thing } from 'directory/index';

Marking as fixed by Ivy but still an issue today, as libraries are still built for VE therefor dependent on the metedata bundler.

We are running into this issue as well (ng-packagr uses this approach rendering the solution useless). Just with a single SharedModule that is reexported through an index file. It breaks. The error is thrown on line 344 of the bundler.ts file const module = this.getMetadata(declaration.module); . declaration is undefined. The declaration is found on the symbol just not on the canonicalSymbol.