-
Notifications
You must be signed in to change notification settings - Fork 13
Blank import aliases when generating with hooks and a custom baseQuery #83
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
Comments
This seems to happening when using TypeScript 4.5. |
Probably caused by dsherret/ts-morph#1221. |
Having the same issue. It's quite critical for out project, because we are relying on RTK query codegen. |
Then please for now use the codegen from a second folder with TS 4.4 installed. I just had an eye operation and can't even see on both eyes yet, it's highly unlikely I'll be able to fix this on short terms notice. |
Didn't work for me. Tried using TS 4.4.4 and 4.1.6 |
Well, some dependency suddenly changed. Our package didn't - and I'm sorry, right now I just cannot debug this. |
Maybe someone from your team can debug this? |
I was able to work around this by installing the
Previously I was running the npx command from the folder with my backend code. This was causing it to use a globally installed version of TypeScript which must have automatically updated yesterday when TS 4.5 was released. |
Could you please give me feedback if #84 works for you as a fix? |
@phryneas is there a way to try it as an npm package without linking etc.? Thanks. |
Unfortunately not - after moving to the RTK monorepo we'll have CodeSandbox package builds for each commit. Right now I'd recommend building locally and installing this with |
I found another small issue, and added testing commands to the PR. |
fixed in https://github.com/rtk-incubator/rtk-query-codegen/releases/tag/v0.5.1 Please note that we will soon release |
When running (roughly) this command in CI today:
I got this error.
I have the same version in local, and that was working until I cleared my npx cache, after which the problem appeared there too.
PS: the problem started occurring today (using 0.5.0), and after a few successful runs in the last few days, without changing the definition.
The text was updated successfully, but these errors were encountered: