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.

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

Road to 1.0 #62

Open
magne4000 opened this issue Feb 25, 2025 · 1 comment
Open

Road to 1.0 #62

magne4000 opened this issue Feb 25, 2025 · 1 comment
Assignees

Comments

@magne4000
Copy link
Member

magne4000 commented Feb 25, 2025

vike-{express,hono,...} packages

  • Allow users to skip specifying a server entry
  • Or users can create a server entry and export app (the first parameter of apply())

vike-server package

  • Require users to have a custom server entry
  • Users will have to manually include a vike-server middleware into the server

Features

All packages above must support the following:

  • +middleware files
  • HMR
  • normal build
  • standalone build
  • custom pageContext
  • sirv (not all servers will be compatible)
  • compress (not all servers will be compatible)

Remaining interrogations

  • How to handle cloud providers like vike-cloudflare?

Steps

@brillout
Copy link
Member

brillout commented Feb 25, 2025

Sounds good.

I wonder what the path of least resistance could be. Maybe this:

  • Rename vike-node => vike-server (and bump major)
  • Move the "last mile" universal-middleware related code (only a couple of LOC) to vike-{express,hono,...}

That's it and relatively easy? I.e. 98% of the code would still live at vike-server.

Allow users to skip specifying a server entry

Would be awesome indeed, although I'd say it's lower prio than the rest.

@magne4000 magne4000 mentioned this issue Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants