Haste module map error with @angular/cli libraries

The library is generated by ng g library @itrulia/dates

    The name `@itrulia/dates` was looked up in the Haste module map. It cannot be resolved, because there exists several different files, or packages, that provide a module for that particular name and platform. The platform is generic (no extension). You must delete or blacklist files until there remains only one of these:

      * `/home/talleane/Documents/@itrulia/dates/dist/itrulia/dates/package.json` (package)
      * `/home/talleane/Documents/@itrulia/dates/projects/itrulia/dates/package.json` (package)

dist is the generated output by ng build @itrulia/dates.

spec looks like this:

import {ReactiveFormsModule} from "@angular/forms";
import {async, ComponentFixture, TestBed} from "@angular/core/testing";
import {AppComponent} from "./app.component";
import {DatesModule} from "@itrulia/dates";

describe("AppComponent", () => {
    let component: AppComponent;
    let fixture: ComponentFixture<AppComponent>;

    beforeEach(async(() => {
        TestBed.configureTestingModule({
            declarations: [
                AppComponent
            ],
            imports: [
                DatesModule,
                ReactiveFormsModule
            ]
        })
        .compileComponents();
    }));

    beforeEach(() => {
        fixture = TestBed.createComponent(AppComponent);
        component = fixture.componentInstance;
        fixture.detectChanges();
    });

    it("should create", () => {
        expect(component).toBeTruthy();
    });
});

I have tried adding

modulePathIgnorePatterns: [
    "<rootDir>/projects"
  ],

This resulted in to Jest not being able to find @itrulia/dates.

[acailly]

I fixed this issue by excluding dist dir in modulePathIgnorePatterns and mapping packages from @myscope to dist folder:

module.exports = {
  ... ,
  modulePathIgnorePatterns: [... , "<rootDir>/dist/"],
  ... ,
  moduleNameMapper: {
    "^@myscope/(.*)$": "<rootDir>/dist/myscope/$1"
  }
};

[ahnpnl]

No, actually in my opinion this is more like user specific requirements and Jest config can help you to handle that. The preset doesn’t take into account of it but only helps to setup base configuration to use Jest with an Angular project. It is similar to the case of configuring paths in tsconfig.json.

For example in my current work project, I did this in tsconfig.json:

"paths": {
      "@archive/*": ["app/archive/*"],
}

and in my Jest configuration I put this:

 "moduleNameMapper": {
      "^@archive/(.*)$": "<rootDir>/src/app/archive/$1",
}

This will help Jest to resolve the path correctly for the tests.

Can you try something similar like that ?