docs: existing links to "VS Code Server" should be updated

[NdagiStanley]

📚 Is your documentation request related to a problem?

The following are the concerned links:

• devtools/docs/content/1.guide/1.features.md

  Line 95 in a6e0bdc

  For more information on the benefits and features of VS Code Server, refer to [the official Visual Studio Code blog](https://code.visualstudio.com/blogs/2022/07/07/vscode-server)

• devtools/packages/devtools/src/integrations/vscode.ts

  Line 151 in a6e0bdc

  description: 'It seems you don\'t have code-server installed.\n\nLearn more about it with <a href="https://code.visualstudio.com/blogs/2022/07/07/vscode-server" target="_blank">this guide</a>.\nOnce installed, restart Nuxt and visit this tab again.',

The existing links point to an outdated post on the "Visual Studio Code" blog here. While there's an updated blog post mentioned in said outdated post; find it here, it's likely that more posts have followed or may could follow.

I suggest linking to the "VS Code Server" documentation page here, instead.

🔍 Where should you find it?

Just where it is. I'm not suggesting that the docs' copy or location should change. Only the link should be updated.

ℹ️ Additional context

No response

[antfu]

I am aware of their newer version of the code server; however, the last time I checked it, because they are moving to the tunnel approach instead of self-host locally, it wouldn't work on Nuxt DevTools because of CORS limits. I am not sure if there would be a solution for that at this moment, so for now, we need to point to the old post for users to follow the legacy approach. If they eventually deprecate that while we can't find a good solution to workaround, we might unfortunately need to remove this feature from Nuxt DevTools.

[NdagiStanley]

Thank you for the response, @antfu!
That's a great argument.

Please note that, the linked blog post claims that "VS Code Server is in private preview" and points a Nuxt user to sign-up:

yet the form is closed and points to the non-legacy approach: https://aka.ms/vscode-server-doc

Therefore, the Nuxt user is eventually sent to the newer approach. I agree with you that if they eventually deprecate and you can't find a good solution to workaround, then you might need to remove this feature from Nuxt DevTools.

In the meantime, maybe having the legacy approach (captured in the linked blog post) documented in Nuxt documentation may suffice. What do you think? I'm happy to help with that effort.