-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot find module '@adminjs/typeorm' or its corresponding type declarations. #61
Comments
has to be |
I tried those options for
I also tried the workaround described in the previous issue #60 and was still getting the error |
Downgrade to v.4 helped |
I tried that as well and got a bit further, though I don't love that path since 5.0.0 has been out for two and half months with no patches to it. 😬 Either way, I'm having a lot of issues related to
|
@sbassin most if not all of our commercial projects use |
I can appreciate that, @dziraf, and thanks for the reply. What information would be most helpful? I will freely admit to being quite inexperienced regarding many the {
"compilerOptions": {
"rootDirs": ["./src", "./test"],
"target": "ESNext",
"types": ["node", "jest"],
"forceConsistentCasingInFileNames": true,
"module": "NodeNext",
"moduleResolution": "NodeNext",
"strict": true,
"outDir": "./dist",
"sourceMap": true,
"esModuleInterop": true,
"experimentalDecorators": true,
"emitDecoratorMetadata": true,
"strictPropertyInitialization": false,
"baseUrl": ".",
"paths": {
"@/*": ["src/*"],
"@test/*": ["test/*"],
"@test-utils/*": ["test/util/*"],
"@factories": ["factories"],
"@factories/*": ["factories/*"],
"@db/*": ["src/db/*"],
"@models/*": ["src/models/*"],
"@resolvers/*": ["src/resolvers/*"],
"@services/*": ["src/services/*"]
}
}
} And here are the dependencies in my "dependencies": {
"@adminjs/express": "^6.0.0",
"@adminjs/typeorm": "^5.0.0",
"@types/express-session": "^1.17.7",
"adminjs": "^7.0.8",
"apollo-server": "^3.12.0",
"apollo-server-express": "^3.12.0",
"auth0": "^3.4.0",
"bcrypt": "^5.1.0",
"chance": "^1.1.11",
"class-validator": "^0.13.2",
"express": "^4.18.2",
"express-jwt": "^8.4.1",
"express-oauth2-jwt-bearer": "^1.5.0",
"gravatar": "^1.8.2",
"jsonwebtoken": "^9.0.1",
"module-alias": "^2.2.3",
"pg": "^8.11.0",
"postgres": "^3.3.5",
"reflect-metadata": "^0.1.13",
"styled-components": "^6.0.3",
"tslog": "3.3.4",
"type-graphql": "^1.1.1",
"typedi": "^0.10.0",
"typeorm": "^0.3.16"
},
Would any more information be valuable? |
@sbassin do you have |
I do not, @dziraf, but I'd be happy to try that later tonight. Thanks. |
Well, that seems to have cleared up a lot of the problems I was seeing. I'm still seeing a number of these issues relating to
|
Hello,
I already seen something similar in the "closed" issues where is a workaround but not a solution.
Is possible to find a solution for this issue.
Node.js v18.16.0
Package,json
tsconfig.json
Thanks for your help
Sam
The text was updated successfully, but these errors were encountered: