We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
when using tsconfig option "module": "Node16", "moduleResolution": "Node16" in a commonJS project orama refuses to import correctly
I'm using these option as per the documentation set in https://www.typescriptlang.org/docs/handbook/modules/reference.html#the-module-compiler-option
the code will not work, as in it doesn't event compile
since orama emits cjs file it should just be able to import the correct one
windows: 11 typescript: 5.4.3 node: v18.20.2 orama: 1.2.11
Environment/OS
if needed I can provide more details when asked
The text was updated successfully, but these errors were encountered:
Faced the same issue, got it working by dynamic import (as a workaround).
const searchFunction = async (data) => { return import("@orama/orama").then(async (module) => { const searchDB = await module.create({ schema: { ... } }); // Implement search logic below }) };
Sorry, something went wrong.
No branches or pull requests
Describe the bug
when using tsconfig option
"module": "Node16",
"moduleResolution": "Node16"
in a commonJS project orama refuses to import correctly
I'm using these option as per the documentation set in https://www.typescriptlang.org/docs/handbook/modules/reference.html#the-module-compiler-option
To Reproduce
the code will not work, as in it doesn't event compile
Expected behavior
since orama emits cjs file it should just be able to import the correct one
Environment Info
Affected areas
Environment/OS
Additional context
if needed I can provide more details when asked
The text was updated successfully, but these errors were encountered: