Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
FindOptionsWhere has no exported member
See original GitHub issueI’m trying to npm run tsc -- --project tsconfig.json but I’m facing this error:
node_modules/nestjs-typeorm-paginate/dist/paginate.d.ts:1:74 - error TS2305: Module '"typeorm"' has no exported member 'FindOptionsWhere'.
- node version: v16.14.0
- npm version: 8.3.1
- tsc version: Version 4.6.3
- nestjs-typeorm-paginate: 4.0.0
Issue Analytics
- State:
- Created a year ago
- Comments:6
Top Results From Across the Web
Module '"typeorm"' has no exported member 'Column ...
When I create the project with the typeorm CLI, It dont recognize the modules and shows in red 'Module '"typeorm"' has no exported...
Read more >error TS2305: Module '"/node_modules/typeorm/index"' has ...
Error: error TS2305: Module '"/node_modules/typeorm/index"' has no exported member 'Like'.
Read more >Module has no exported member error in TypeScript
The error "Module has no exported member" occurs when we try to import a member that doesn't exist in the specified module. To...
Read more >Module '"@microsoft/sp-http"' has no exported member ...
Hi, I am trying to use SPHttpClientBatch class and I am getting the error: Module '"@microsoft/sp-http"' has no exported member ...
Read more >Unable to resolve "@pnp/graph"' has no exported member ...
The use of graph was changed to graphfi in PnPjs v3. enter image description here.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I didn’t remember whether it presented the warning msg or not. But apparently, build failed due to the type error. I think it’s okay however, typeorm should be updated instead. we will stick to v3.2.1 until we’d update typeorm in the app.
@CrazyOptimist still the same with 4.0.1? It should’ve presented a warning as the peer dependancy doesn’t match no?