Skip to content
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

When opening a page of nuxt3 in a qq app window on an apple phone, it reports 500 error code #25956

Closed
mumuchongya opened this issue Feb 26, 2024 · 7 comments

Comments

@mumuchongya
Copy link

Environment

Reproduction

uconf.com

Describe the bug

500
When opening a page of nuxt3 in a qq app window on an apple phone, it reports 500 error code

Additional context

No response

Logs

No response

@markthree
Copy link

@mumuchongya
Although this is not a recommended practice, you can set up in package.json

"resolutions": {
  "ofetch": "npm:[email protected]"
},
"overrides": {
  "ofetch": "npm:[email protected]"
}

After that, re-run npm install and package it again. This should temporarily solve your problem.

@mumuchongya
Copy link
Author

@mumuchongya Although this is not a recommended practice, you can set up in package.json

"resolutions": {
  "ofetch": "npm:[email protected]"
},
"overrides": {
  "ofetch": "npm:[email protected]"
}

After that, re-run npm install and package it again. This should temporarily solve your problem.

Thank you! This is the best solution I've used so far!

@markthree
Copy link

If someone doesn't have high stability requirements, they can use this module → markthree/nuxt-fix-ofetch

@YunYouJun
Copy link
Contributor

unjs/ofetch#366

@xiaoruo-lin
Copy link

I also hope the author can solve this problem of QQ browser

@danielroe
Copy link
Member

danielroe commented Jun 14, 2024

This should be resolved in the latest v3.12.1 via #27441. Let me know if not, and I will happily reopen. 🙏

@xiaoruo-lin
Copy link

此问题应在最新的 v3.12.1 中通过#27441得到解决。如果没有解决,请告诉我,我会很乐意重新打开。🙏

Wow, I'm so surprised, thanks for your reply, I'm even more happy that you are going to deal with this issue, thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants