server component roadmap
We have experimental support in Nuxt 3 for both island components and server-only components (which are implemented using islands) - see https://github.com/nuxt/framework/pull/5689 and https://github.com/nuxt/framework/pull/9972 for initial implementations and https://github.com/nuxt/nuxt/discussions/17956 for initial partial RFC. There are a number of future linked improvements. This issue is to track those and provide some place to document the linking story, purpose and usage of server components within Nuxt. ## Purpose and usage Currently we are collecting use patterns to ensure that the final API and implementation for server components is useful. But the following are some benefits we are exploring: 1. security and direct access to server APIs within certain components 2. separate caching strategies for individual chunks of HTML 3. leaner bundle size (keeping some dependencies solely on the server, e.g. syntax highlighting) 4. extensibility 5. rendering individual components within other modules or server routes (e.g. for component previews, OG images, PDF downloads, etc.) 6. ... Comments and suggestions are very welcome. - [x] Allow async components - https://github.com/nuxt/nuxt/issues/18500 - [x] Client-side interactivity - https://github.com/nuxt/nuxt/issues/19765 - [x] remove server component content from payload and prefetch on route transition: https://github.com/nuxt/nuxt/pull/21461 - [x] Hybrid/remote/streaming sources for server components - https://gith
Posted by danielroe on Mar 17, 2023, 3:09 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
support (Sysadmin)
Support connecting to remote devcontainers (devcontainer on remote host)
Option to use Waffle menu or links displayed normally
I also attempted to package ROCM on musl.
But why is there no such pushback agains linux kernel?
OpenCode Support
Upcoming changes to the tado° API
Allow Mac users to use Apple native containerization
Support for the Containerization Framework on macOS
server component roadmap
We have experimental support in Nuxt 3 for both island components and server-only components (which are implemented using islands) - see https://github.com/nuxt/framework/pull/5689 and https://github.com/nuxt/framework/pull/9972 for initial implementations and https://github.com/nuxt/nuxt/discussions/17956 for initial partial RFC. There are a number of future linked improvements. This issue is to track those and provide some place to document the linking story, purpose and usage of server components within Nuxt. ## Purpose and usage Currently we are collecting use patterns to ensure that the final API and implementation for server components is useful. But the following are some benefits we are exploring: 1. security and direct access to server APIs within certain components 2. separate caching strategies for individual chunks of HTML 3. leaner bundle size (keeping some dependencies solely on the server, e.g. syntax highlighting) 4. extensibility 5. rendering individual components within other modules or server routes (e.g. for component previews, OG images, PDF downloads, etc.) 6. ... Comments and suggestions are very welcome. - [x] Allow async components - https://github.com/nuxt/nuxt/issues/18500 - [x] Client-side interactivity - https://github.com/nuxt/nuxt/issues/19765 - [x] remove server component content from payload and prefetch on route transition: https://github.com/nuxt/nuxt/pull/21461 - [x] Hybrid/remote/streaming sources for server components - https://gith
Comments (0)
No comments yet. Start the discussion.