-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
NextJS - Cannot read properties of undefined (reading 'transactionbuilderconfigbuilder_new') #174
Comments
Could you try out Lucid |
@alessandrokonrad Greetings! I receive the same error, using Chrome v113, node v18.16.0 Vue3 and lucid version 0.10.2. I also installed wasm-loader v1.3.0., unfortunatelly with no result. I've tried different versions of lucid, the error remains. Can it be a problem with configuration? I am open for discussion in discord if needed. Thank you in advance! |
Getting this as well on
It seems like the top level await isnt working, or its not being detected properly when |
Download one of these templates: https://meshjs.dev/starter-templates and use it as a starting point. I believe the setup works with lucid, because both libs use cardano serialization lib. |
I am getting the same error with angular, any solution will be much appreciated. |
any updates on this also having same issue next js 13.4 and lucid 10.6 |
I'm running into this issue in angular as well. |
Running into this issue as well with React when using webpack for bundling, any idea how we can solve it or what causes it? |
This appears to be an issue with next fetching static content (see attached images). Any reasons this might be happening @alessandrokonrad ? |
Next.JS disallows relative imports since 12.0.1 (see https://nextjs.org/docs/messages/middleware-relative-urls for more information). So, we need to sniff out if we are in the NEXTJS environment and if so, use the fallback URL. This should resolve: spacebudz#174 [ Testing: deno task build ]
Opened #220 which might provide a fix. Seems to be an issue with middleware usage of lucid specifically. |
Next.JS disallows relative imports since 12.0.1 (see https://nextjs.org/docs/messages/middleware-relative-urls for more information). So, we need to sniff out if we are in the NEXTJS environment and if so, use the fallback URL. This should resolve: spacebudz#174 [ Testing: deno task build ]
Next.JS disallows relative imports since 12.0.1 (see https://nextjs.org/docs/messages/middleware-relative-urls for more information). So, we need to sniff out if we are in the NEXTJS environment and if so, use the fallback URL. This should resolve: spacebudz#174 [ Testing: deno task build ]
Next.JS disallows relative imports since 12.0.1 (see https://nextjs.org/docs/messages/middleware-relative-urls for more information). So, we need to sniff out if we are in the NEXTJS environment and if so, use the fallback URL. This should resolve: spacebudz#174 [ Testing: deno task build ]
Getting similar issues with Next.js 13. Any solution yet? |
I pushed a Pull Request (#220) for this and published it to this npm module: https://www.npmjs.com/package/lucid-cardano-nextjs |
Why this is still not fixed? I'm also having this error |
I'm seeing this error when I try and instantiate Lucid.new(...). I've tried this with and without
use-cardano
. I've also verified that I'm getting the correct values back from the blockfrost.getProtocolParameters(). The network I'm trying to hit isPreview
Error stack:
Any help is appreciated.
tsconfig.json
next.config.js
Package.json
Update: Looks like every works correctly on version 0.7.2
The text was updated successfully, but these errors were encountered: