-
Notifications
You must be signed in to change notification settings - Fork 392
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
bug: @core/llamaindex
doesn't allow access to various schemas
#987
Comments
change module resolution to node16 or bundler in your tsconfig |
@himself65 thanks! switching to bundler has resolved it |
nit: always use |
@himself65 I'm trying to find a work around right now but setting to bundler might not always be possible more context: building or azure functions app |
I don't have much further idea about this, but this is ts old behavior. But whether you update your tsconfig.json, do some patches to make type check happy, or use a bundler to a single js file before releasing to the Azure function app. maybe related issue: microsoft/TypeScript#46452 llamaindex-ts targeting to > node.js 18, and recent typescript > 4.7 so I don't want to support legacy node and ts |
@himself65 apologies totally forgot to update you on this. That's fair and very reasonable not want to support anything below node18. In the end I managed to work around everything bit by bit to get the build working. The one thing that was frustrating and I figured out in the end was, prettier had to be re-configured too, renaming it's config from |
do you mean cjs to esm? |
Yep |
Attempting to import the following from
@core/llamaindex
and gettingCannot find declarations
Document
Metadata
BaseNode
MetadataMode
NodeWithScore
any tips @himself65 ?
P.S. I think this is a good direction, just need to figure out the above
The text was updated successfully, but these errors were encountered: