feat(nuxi): call nuxt listen hook for dev

[harlan-zw]

🔗 Linked issue

nuxt/bridge#149

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• [] ✨ New feature (a non-breaking change that adds functionality)
• [] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

The listen hook is a feature from nuxt v2 that is typed in nuxt v3. but nothing calls it (as far as I can tell).

It's a useful hook to expose the server used for local development, giving module authors functionality to see the server address and hook into the server if needed.

Specifically a module I'm working on needs it, this is the equivalent nuxt 2 code.

nuxt.hook('listen', (ctx) => {
  setServerContext({
    url: ctx.listeners[0].url,
    server: ctx.listeners[0].server,
    app: ctx.app,
  })
})

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly. - no hook documentation section, needs it's own page

[netlify]

✔️ Deploy Preview for nuxt3-docs canceled.

🔨 Explore the source changes: 230df8d

🔍 Inspect the deploy log: https://app.netlify.com/sites/nuxt3-docs/deploys/61e6a32fca88da0007a2841c

[danielroe]

This looks good to me.

Some context: nuxt/bridge#149.

[pi0]

Thanks 💚

[fabianwohlfart]

Sorry, but is this already available? I am running nuxt 3.0.0-27398533.8edd481 and in build/start listen does not get fired.

[danielroe]

@fabianwohlfart This PR only adds this hook in dev.

[fabianwohlfart]

@danielroe Is it possible at the moment to somehow hook onto the server and start a service, especially Socket.io? I have read nuxt/bridge#149 and not sure where things are or if i am just to blind to find the right resources...

[lewebsimple]

Is the listen hook only called in development mode ?

Also, wouldn't it make sense to have listen:before / listen:after so we can initialize things before the server actually starts to listen ? This seems like a common use case for stuff like pre-establishing database connections

See this discussion