-
Notifications
You must be signed in to change notification settings - Fork 104
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
6.5.0 update error #215
Comments
I don't see any errors when I build my master(6.5.0) branch using node |
I have the same problem, and using version |
./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.`);
| } |
It's probably an issue with the
|
@giyeol @woohyun1031 it looks like that line was last changed in nodejs/undici#2743, which was part of |
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. |
Describe the bug
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.
Screenshots
![스크린샷 2024-03-05 오후 1 04 41](https://private-user-images.githubusercontent.com/94066263/310010622-57c37b30-9ec5-4c11-8403-05bc3033aab4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ0MTY5NzgsIm5iZiI6MTcyNDQxNjY3OCwicGF0aCI6Ii85NDA2NjI2My8zMTAwMTA2MjItNTdjMzdiMzAtOWVjNS00YzExLTg0MDMtMDViYzMwMzNhYWI0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODIzVDEyMzc1OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI4ZjA0ZTIyYjlmOWZlNTg0ZmQ2YWUyNWRjNzRkMWU0ZDE5NmVhNzEzYjA3OTkxNTY4YzY4NTJjNDFhYjkxMWEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.0hycCUpw7IhXwR5ctFXYBc0hMQOLUIenxIeC87aEFwI)
Environment
The text was updated successfully, but these errors were encountered: