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

Use Vite to process Node.js server code (e.g. Express.js) #169

Closed
brillout opened this issue Oct 11, 2021 · 4 comments
Closed

Use Vite to process Node.js server code (e.g. Express.js) #169

brillout opened this issue Oct 11, 2021 · 4 comments
Labels
enhancement ✨ New feature or request

Comments

@brillout
Copy link
Member

So far the recommended way is to use vanilla Node.js (or with ts-node) to run the user's Node.js server code (e.g. Express.js).

The reason being that Vite has some troubles with server-only deps (vitejs/vite#4921, vitejs/vite#4230).

But these will get fixed and then we should start using Vite for server code as well. E.g. vite-node (antfu/vite-node#2), tsm, or esno. (antfu/vite-node#2 (comment).)

@brillout brillout added the enhancement ✨ New feature or request label Oct 11, 2021
@stychu
Copy link

stychu commented Jul 28, 2022

Hey @brillout. Wanted to ask if this is something on the radar? I kinda struggle to make this work with vite.
Alternative would be nodemon but I wish it couuld be done with vite and ideally with vite features applied

@brillout
Copy link
Member Author

Yes, it is on the Radar.

Long/middle term: HatTip.

In the meantime you can use vavite. See the vite-plugin-ssr + vavite example.

@stychu
Copy link

stychu commented Aug 1, 2022

Thanks for the suggestions. Vavite seems like the deal. At least it's working 👌

@brillout
Copy link
Member Author

Closing in favor of #562.

@brillout brillout closed this as not planned Won't fix, can't repro, duplicate, stale Apr 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants