Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ERROR [proxy] connect ENOENT /var/folders/ff/../nitro/worker-...sock

See original GitHub issue

Environment

------------------------------
- Operating System: `Darwin`
- Node Version:     `v16.13.1`
- Nuxt Version:     `3.0.0-27319101.3e82f0f`
- Package Manager:  `yarn@1.22.17`
- Bundler:          `Vite`
- User Config:      `srcDir`, `meta`, `css`, `components`, `buildModules`, `publicRuntimeConfig`
- Runtime Modules:  `-`
- Build Modules:    `@vueuse/nuxt@7.3.0`, `nuxt-windicss@2.1.1`, `@tailvue/nuxt@0.1.50`
------------------------------

Reproduction

Just yarn dev on any project with the latest of nuxt3

Describe the bug

doing a yarn dev I eventually get

 ERROR  [proxy] connect ENOENT /var/folders/ff/f_1wmhd550g87b1czghwdpyh0000gn/T/nitro/worker-55586-1.sock               17:05:02

  at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)

Additional context

Basically happens w/in 20-30m on dev - restart fixes it

Logs

No response

Issue Analytics

State:
Created 2 years ago
Reactions:7
Comments:9 (3 by maintainers)

Top GitHub Comments

2reactions

maybebotcommented, Dec 20, 2021

Operating system: Ubuntu 20.04
Node version: v14.17.0
Nuxt version: 3.0.0-27313139.1c88580
Package manager: yarn@1.22.5

Any error during SSR seems to cause this. I had a reference to “document” that throws a document is not defined (which makes perfect sense in SSR). Once removed the error above does not show up.

If I put a throw { err: 'something' }; in my code the same happens.

If I first-load with SSR a different page (with not errors) and then go to the page with the error, my code will error out as expected client-side (or not, in the case of document being undefined) but the ‘worker sock’ error is not present.

1reaction

danielroecommented, Apr 15, 2022

Okay, I’m going to close the issue as tentatively fixed 🤞

Please let me know if it reoccurs, ideally with a reproduction or more info, and we’ll reopen & investigate…