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
Hi. I always use this library successfully. Thank you!
"After upgrading open-graph-scraper from version 6.3.2 to 6.5.0 in the current Next.js 14 project, a compilation error occurred during the build.
This issue was observed on both client and server components.
While tracing the error, it was identified that the problem originated in the 'lib/web/fetch/util.js' file, and it was noted that undici, a dependency of open-graph-scraper, was also updated.
Testing with another Next.js project revealed that the error started occurring from a specific version of open-graph-scraper onwards.
As a result, I downgraded back to the previously used version 6.3.2.
I'm having difficulty pinpointing the exact cause of this error, and I'm curious if you have any insights into why it might be happening.
I have similar problem, and using version v20.11.1.
./node_modules/.pnpm/undici@6.7.0/node_modules/undici/lib/web/fetch/util.js
Module parse failed: Unexpected token (608:63)
| // 5. If object is not a default iterator object for interface,
| // then throw a TypeError.
>if (typeof this !== "object"|| this === null ||!(#target in this)) {| throw new TypeError(`'next' called on an object that does not implement interface ${name} Iterator.`);| }
@giyeol@woohyun1031 it looks like that line was last changed in nodejs/undici#2743, which was part of undici@6.7.0. I would recommend opening a issue/pull request with undici. I'm still not able to reproduce the problem.
It looks like the undici team is aware of the issue -> nodejs/undici#2954 and are pushing to fix this in nextjs. Closing this for now since there isn't a way this can be fixed in OGS, please follow up with the nextjs team.
Activity
jshemas commentedon Mar 6, 2024
I don't see any errors when I build my master(6.5.0) branch using node
v20.10.0. Can you make a example repo that has the problem?giyeol commentedon Mar 6, 2024
I have the same problem, and using version
v20.11.1.giyeol commentedon Mar 6, 2024
giyeol commentedon Mar 6, 2024
It's probably an issue with the
undicipackage. I fixed it with the following modification.jshemas commentedon Mar 6, 2024
@giyeol @woohyun1031 it looks like that line was last changed in nodejs/undici#2743, which was part of
undici@6.7.0. I would recommend opening a issue/pull request withundici. I'm still not able to reproduce the problem.v9ai commentedon Mar 8, 2024
having the same error
jshemas commentedon Mar 16, 2024
It looks like the undici team is aware of the issue -> nodejs/undici#2954 and are pushing to fix this in nextjs. Closing this for now since there isn't a way this can be fixed in OGS, please follow up with the nextjs team.