Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pluggable or Replaceable SSR and client runtimes #49

Open
ChristopherBiscardi opened this issue Nov 3, 2020 · 0 comments
Open

Pluggable or Replaceable SSR and client runtimes #49

ChristopherBiscardi opened this issue Nov 3, 2020 · 0 comments

Comments

@ChristopherBiscardi
Copy link
Collaborator

ChristopherBiscardi commented Nov 3, 2020 •
edited
Loading

The SSR and client-side runtime could be pluggable.

Open Questions

  • What would this enable us to do?
    • Maybe Vue/Svelte/etc support?
    • Maybe framework-specific routers
      • Code is already rendered to JS files, so it's possible that with features like Suspense you could SSR and rehydrate into a client-side rendered application with React Router
  • What would it prevent us from doing?
  • If future Toast is runnable in a serverless function on-demand, would we be able to support all pluggable runtimes or would some be "serverless supported"? Does it matter?
  • How does it affect page-wrapper/component removal? What would an "up to spec" wrapper look like? How do we make sure we communicate that from npm packages to the toast project and more.
    • setDataForSlug("/", { component: null, wrapper: null, data: {}})
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ChristopherBiscardi