-
Notifications
You must be signed in to change notification settings - Fork 28
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
TypeError: namingStrategy.tableName is not a function #8
Comments
Hey, could you provide a reproduction repo? I don't see where the error can come. |
@PaulMest If you haven't resolved this, it also might be worth checking that you are emitting to es6+ with tsc. es5 and below has quirks with TypeScript and classes annoyingly. Has solved issues not too dissimilar before. |
I have the same issue. But then I extracted the class into another package (symlinked via npm install ../path) and ran into this issue. I thought it myght be a problem with my implementation or typescript configuration, so I downloaded the code and tried it with the repo-content. Still the same problem. Then I tried to use the package tar from npmjs.com. First I put it next to my project and installed it with
This created a symlink in test/node_modules. When I tried to run my code the first time, it came up with this error:
Then I installed the dependencies in typeorm-naming-strategies The next Error was this:
When i deleted the symlink from node_modules and placed a copy of the tar content in node_modules everything worked fine again. So I think it has something to do with symlinks and typescript and not really with this package, but if you have an idea why this issue occures, it would be very helpful. I think typescript needs to handle the dependencies relative to the folder, where the symlink is placed and not to where the original folder is, but I don't know how to tell typescript this. |
If I upgrade TypeORM from
0.2.22
to0.2.26
or0.2.27
I get the following error:... any idea what could be the problem?
The text was updated successfully, but these errors were encountered: