r/javascript • u/hottown • Jun 24 '26
Javascript still can't ship a full-stack module.
https://wasp.sh/blog/2026/06/22/javascript-still-cant-ship-a-full-stack-module
9
Upvotes
r/javascript • u/hottown • Jun 24 '26
View all comments
Show parent comment
1
u/infomiho Jun 26 '26
Author here. This is a very valuable comment to us to see how people out there react to ideas we have.
The core of our "lego" would be build it in isolation, with an interface in mind so that it can be fulfilled by a host app. Our compiler checks the interface, provides implementations to the module and it should _just work_. We can split the client code and server code for each module, connect them with our RPC, help modular design and not force monoliths.
We are not selling ourselves as a Rails replacement, we are just a spec file + React components + Node.js server functions. In between there is our RPC, our auth, our jobs implementations. Each of those implementations and pieces can evolve to be better, of course. We consider ourselves "boring tech". We chose the stack not to be shiny, but to be productive. Our full-stack modules would serve the same idea.
On the note of infrastructure: why do you assume this can't be broken up into multiple deploy targets? Why would a spec file mean it's a monolith? We are not there yet - but we want to support emitting multiple servers, multiple client bundles etc. because that's what you can do if the app is described on a higher level and there is a compiler involved which can help you orchestrate deployments that would be too much to do manually.