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.

Sign up for GitHub

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

Jump to bottom

Nuxt DevTools error #52

Closed
frasza opened this issue Mar 11, 2024 · 3 comments
Closed

Nuxt DevTools error #52

frasza opened this issue Mar 11, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@frasza
Copy link

frasza commented Mar 11, 2024 •
edited

Hey 👋

Recently I have set up new Nuxt project with fonts module and based on v 0.2 I am receiving regular errors in console:

 ERROR  [unhandledRejection] [birpc] timeout on calling "nuxt-devtools-fonts:exposeFonts"  11:08:21  

  at Timeout._onTimeout (/C:/Users/zanfr/Work/Code/SmartCity/web-next/node_modules/birpc/dist/index.mjs:42:23)
  at listOnTimeout (node:internal/timers:573:17)
  at process.processTimers (node:internal/timers:514:7)

The errors seems to be displayed on regular interval on it own after dev server is running for some time. Can't really say.
If needed I will try to give reproduction, altho, its fresh Nuxt project.
@danielroe danielroe added the bug Something isn't working label Mar 11, 2024
danielroe added a commit that referenced this issue Mar 11, 2024
@danielroe
fix(devtools): don't wait for callback from exposeFonts
35758d6 
#52
@danielroe
Copy link
Member

I can't reproduce (I suspect it's a Windows issue with devtools) but I've pushed a possible fix in 0.2.1. Let me know if it resolves it for you.

I note that @harlan-zw ignores errors and wonder if he encountered something similar:

https://github.com/nuxt-modules/og-image/blob/be96e004c73ee88e8305053c41bcfa3f53c60d60/src/build/devtools.ts#L52-L53

@harlan-zw
Copy link

harlan-zw commented Mar 12, 2024 •
edited

As far as I understand it, when sending rpc messages on Nuxt events, there may be no client connected, which ends up throwing an error. To avoid this I just ignore the errors, not ideal but couldn't find a solution.

@danielroe
Copy link
Member

I'm closing this as I think we've resolved with asEvent. Let me know if it reoccurs for you...

@dosubot dosubot bot mentioned this issue May 4, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@harlan-zw @frasza @danielroe