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
No longer able to build TS project after update to 9: Cannot find module './lib/api/typesWithBodyKey' or its corresponding type declarations. Quick look at the package: the file no longer exists.
Update: Deleting the line from the index.d.ts manually does the trick.
Last working version
8.18.2
To reproduce
create a file foo.ts
import{Client}from'@elastic/elasticsearch';
run
npx tsc foo.ts
Expected behavior
i expect this to build
Node.js version
20.18.3
TypeScript version
5.8.3
Elasticsearch client version
9.0.1
Elasticsearch server version
9.0.1
Operating system
Debian
Any other relevant environment information.
No response
The text was updated successfully, but these errors were encountered:
This is mentioned in the 9.0 breaking changes, at least indirectly. typesWithBodyKey is indeed no longer supported and that is intentional.
I've updated the breaking changes does in #2839 to mention this more explicitly. If you need typesWithBodyKey, it is suggested to keep using an 8.x client until you are ready to remove its usage.
Got it, misunderstood what you meant. That was actually in #2821 recently but a patch release has not been published since then. I'll publish 9.0.2 today with that fix.
Uh oh!
There was an error while loading. Please reload this page.
Regression report
No longer able to build TS project after update to 9:
Cannot find module './lib/api/typesWithBodyKey' or its corresponding type declarations.
Quick look at the package: the file no longer exists.Update: Deleting the line from the index.d.ts manually does the trick.
Last working version
8.18.2
To reproduce
create a file
foo.ts
run
Expected behavior
i expect this to build
Node.js version
20.18.3
TypeScript version
5.8.3
Elasticsearch client version
9.0.1
Elasticsearch server version
9.0.1
Operating system
Debian
Any other relevant environment information.
No response
The text was updated successfully, but these errors were encountered: