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
Using Next.js App Dir with Builder V2 #3235
Comments
We ran into this (we're on NextJS 14.1) following the same instructions, the workaround is to manually declare the module (it is there in the package just not declared?) Add something like
|
Yes, there is an issue with the types not propagating correctly for certain TS configurations. We will investigate this, thanks for reporting. The import itself should work correctly on the JS side. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
In this example, provided by Builder.io, it is suggested to use the following code snippet:
However, initializeNodeRuntime does not seem to exist within the module, as evidenced by the following error screenshot:
This issue occurs despite following the recommended setup. I would prefer to use this package due to its compatibility with the pages router in my project, which precludes using the Next.js SDK.
Additionally, I attempted to use the directive 'use client' at the top of the file to handle client-side custom components, but this approach failed to resolve the issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Additional context
Using Next.js version 13.4.8 and following the guide provided in the Builder.io GitHub repository.
The text was updated successfully, but these errors were encountered: