weightless | High-quality web components with a small footprint | Web Framework library

This blog post I found today shows something like this for React. He starts with a node project and then within that he creates a react project in a subfolder. Plus some proxy config stuff.

I wasn't this clever about 10 days ago but here's what I did for Vue.

1. Created a Vue project
2. Built it for production
3. Added a package.json and a server.js in the dist folder created by the Vue build process
4. The package.json contains these two lines: "postinstall": "npm install express" and "start": "node server.js"

And voilá! Express listens on 8081 internally (but translated to 80/443 by Heroku) and I can get a response in the Vue frontend from the Node backend. So technically it works. But I don't feel it's a nice solution. Kind of messy, smells like desperate hacking and tinkering.

The point is, of course, to avoid having two different Heroku pods for an otherwise small, almost weightless personal project. One for the frontend part and one for the backend.

Can you show me anything better?