Typescript type missmatch when creating external module

Question

I am using TypeScript and creating an API using nestjs and typeorm. Some of the modules in the project are made reusable by extracting them into its own node module. This is causing the Repository type in the external module to not be the same type as the Repository type inside the original package. So when using the external module I get the error

Argument of type 'import("/Users/user/project/node_modules/typeorm/repository/Repository")
.Repository<import("/Users/project/src/user/user.entity").User>' 
is not assignable to parameter of type 
'import("/Users/user/my-module/node_modules/typeorm/repository/Repository")
.Repository<import("/Users/project/src/user/user.entity").User>'.

The typeorm package is listed as a peerDependency in the node package so it should always be the same.

Kim Kern · Accepted Answer · 2019-02-18 14:04:02Z

2

Your external library seems to have its own type definitions. In this thread, it is suggested to map imports to a folder under node_modules manually in your package.json:

"paths": {
  "typeorm": ["node_modules/typeorm"],
  "typeorm/*": ["node_modules/typeorm/*"]
}

This might only be an issue when using npm link.

edited Feb 18, 2019 at 14:04

answered Feb 18, 2019 at 13:08

Kim Kern

61.1k20 gold badges221 silver badges215 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

rablentain Over a year ago

Ops, that was actually a typo from me... the Repository is imported from different paths but not the User type.

Kim Kern Over a year ago

Ah ok. :) Did you install your package from npm or did you use npm link?

rablentain Over a year ago

I used npm link

Collectives™ on Stack Overflow

Typescript type missmatch when creating external module

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related