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

Migrate away from the embedded Express server, embrace pure Vite plugins implementation #5

Open
JulianCataldo opened this issue Jul 27, 2024 · 0 comments

Comments

@JulianCataldo
Copy link
Contributor

JulianCataldo commented Jul 27, 2024

This should not be too difficult, but that will make Gracile a bit less personalized regarding dev/build lifecycle.

Some of the benefits are :

  • User can "augment" an existing Vite project with Gracile
  • It's becoming a pattern, since Remix opted for this approach
  • That will shrink deps. by a good bit. Express is definitely too heavy with a deep dep-tree.
  • Internal sources will be fairly simplified.
  • Some CLI entrypoint will become obsolete
  • Tests should be more stable. For now, Gracile runtime can be fiddly to start/stop, especially when a crash occurs (stuck)

Custom CLI entrypoint will have to be preserved for launching the Vite Runtime when using the server output with user provided server instance (loadable from a file entrypoint option, still undocumented).

@JulianCataldo JulianCataldo changed the title Migrate away from an embedded Express server, embrace pure plugins implementation Migrate away from an embedded Express server, embrace pure Vite plugins implementation Jul 27, 2024
@JulianCataldo JulianCataldo changed the title Migrate away from an embedded Express server, embrace pure Vite plugins implementation Migrate away from the embedded Express server, embrace pure Vite plugins implementation Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant