You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
used the search to make sure that a similar issue hasn't already been submit
Description
When generating the routes from my project using tsoa v6.2.1 (typescript 5.3.3) I get the following error:
Generate routes error.
GenerateMetadataError: This node kind is unknown: 241
At unknown position...
This was caused by '<unknown name>'
This used to work fine for tsoa v5.1.1
Steps to Reproduce
Our code is a bit complex so I could not get the chance to create a minimal example that reproduces this issue. I also grepped the code to understand why we would get a This node kind is unknown error. Could you explain to me how this could happen?
One thing to note is that we do use yarn workspaces and we do have some interfaces defined in a shared package between our frontend and backend. Could this be causing issues?
Context (Environment)
Version of the library: 6.2.1
Version of NodeJS: 20.11.0
Typescript: v5.3.3
Confirm you were using yarn not npm: [x]
Though keep in mind that we are using yarn v4.1.1
The text was updated successfully, but these errors were encountered:
Sorting
I'm submitting a ...
I confirm that I
Description
When generating the routes from my project using tsoa v6.2.1 (typescript 5.3.3) I get the following error:
This used to work fine for tsoa v5.1.1
Steps to Reproduce
Our code is a bit complex so I could not get the chance to create a minimal example that reproduces this issue. I also grepped the code to understand why we would get a
This node kind is unknown
error. Could you explain to me how this could happen?One thing to note is that we do use yarn workspaces and we do have some interfaces defined in a shared package between our frontend and backend. Could this be causing issues?
Context (Environment)
Version of the library: 6.2.1
Version of NodeJS: 20.11.0
Typescript: v5.3.3
Though keep in mind that we are using yarn v4.1.1
The text was updated successfully, but these errors were encountered: