webpack-dev-middleware VS restfuncs

Are you using webpack? If so, they have a middleware for exactly this case: https://github.com/webpack/webpack-dev-middleware. The example there should be added to your express script with some form of conditional statement to use express.static in your deployment and webpack-dev-middleware in dev.

It looks like this should have been fixed back in 2017: https://github.com/webpack/webpack-dev-middleware/issues/229

Meteor-Webpack integrates webpack-dev-middleware and webpack-hot-middleware to benefit HMR in your project. The only thing you have to do is enabling this feature just like any other Webpack project;

Putting restfuncs into the round (as the communication lib).

Hi, finally, after a complete redesign of the API, i'm releasing the new 2.0 Version of Restfuncs. Much effort went into the CSRF protection, which i'm kind of proud now, to be one lib that does take much care about this. Still it's a little work-in-progress, as you see, but if you like, you can already start using it and wait, til it's production ready (+ help the typescript-rtti guys to get that lib stable ;) ). The Restfuncs API should be stable and stay on 2.x major version for a while.

OK, that's cool. Looking for something for the restfuncs lib. Currently i'm using typescript-rtti but i'm open to such stuff if the security is good. And fast validation sounds very very good ;)

Here's one library that i'm making for that. Currently it's focused to make functions callable via RPC. But i'm working on a comprehensive REST interface currently. It's already in the docs on the github repo. Hope that is kind of what you are looking for.

See this example and use the dev_faster... run script. It uses a dev/production switch to see if it should run the devserver or host the pre-build static files as you see when you look at server.ts

Yes, behaviour will also be documented in the library's doc under security (not yet done, cause i'm the middle of writing) The library is all about that, so no maintainer will quickly change those core security lines without having understood them. Additionally i've written cross site security testcases which test every line of these ;)

Here's a simple sample project which host the vite devserver inside express for development (so you don't have a chaos with different processes / ports / origins). This should be the way to go.

Or, for a quick client-server app, use this

See this example starter application stack, with client/server communication, cramped down to a ridiculously few lines of code / files - you can't underbeat that.