fix: use listhen's publicUrl if available

[farnabaz]

🔗 Linked issue

❓ 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

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
content-docs	Ready	Preview	Sep 1, 2025 7:53am

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/content@3500

commit: 9463608

[cloudflare-workers-and-pages]

Deploying content with    Cloudflare Pages

Latest commit:	9463608
Status:	✅  Deploy successful!
Preview URL:	https://5c4ecc2f.content-f0q.pages.dev
Branch Preview URL:	https://fix-websocker-public-url.content-f0q.pages.dev

View logs

[hendrikheil]

Great work! I verified this works, you just have to specify watch.port and watch.publicUrl where publicUrl: wss://{domain}

[farnabaz]

@dargmuesli I think this PR also affect/help you, but it should not break the current behavior.

[maximepvrt]

publicConfig.wsUrl = (websocketOptions.publicURL || process.env.publicURL || listener.url).replace('http', 'ws')

to use option --publicURL defined by the nuxt dev command.

[farnabaz]

Have you tries this?
Public URL of websocket and Nuxt are different, since the module creates its own server for websocket, using same publicURL will cause issue.

[maximepvrt]

It’s actually only the port that is different, not the public URL.

[farnabaz]

It’s actually only the port that is different, not the public URL.

We are passing the whole url to client and we don't change the port. So sharing same url means calling to the same port.

We can do it by adding port to publicUrl in publicConfig.wsUrl = (websocketOptions.publicURL || listener.url).replace('http', 'ws') but the end result will not be same.

[maximepvrt]

Laravel Valet proxies allow binding a domain to a service running on a specific port, but they don’t support handling multiple services with different ports.

Example:

monsite.test    => https://localhost:3000
monsite.test:4000 => https://localhost:4000 (not supported)

That’s why I’d rather keep using https://localhost:4000 directly for Hot Content Reload, to avoid CORS issues with websockets.