It seems like the person is wading in a pool of excrement of their own choosing.
1. Node.js or package.json or Vue.js or Nuxt.js issues or Ubuntu C library issues
2. Debugging and customizing pre-built CSS frameworks
First of all they're running a very simple blog, a SSG should be more than sufficient for their usecase. If for some reason the engineer in them decides they want to ship their own, which I completely relate to, all these problems come packaged with that decision.
Even then, after browsing their site, it's very barebones, nothing more than a router and a md -> html transformer is needed.
You don't even need a custom CSS framework for whatever this is, all the components on their website are so simple a single CSS file < 300 lines (I'm being very liberal) including media queries should do the trick.
Regarding DNS, in my 15 years of experience building/deploying websites there have been very few cases where setting up DNSs was a pain and that was only when I was using shady webhosts to minimise cost.
Can't comment much on caching, but I remember with Jekyll you can just append `{{ site.time | date: '%s%N' }}` to your asset and lo behold ez cache busting.
I host several statically built websites on a cheap VPS. DNS and SSL was configured once, Pelican + Rsync bungs up the new posts whenever I need them.
The site itself handles hundreds of requests daily without breaking a sweat. The server has an up time approaching 2 years. I’ve had to maintain it minimally since then; APT updates break nothing, thanks Debian.
Maybe my tastes are different, but I enjoy playing with the scripts, the config, tweaking the CSS here and there. The risks are tiny and the payoff is I have a fun site that a couple of other people enjoy.
All of the effort to create sites like mine is in the initial configuration; lifetime maintenance is minimal. Chasing security obstructions and NPM build errors every week, I don’t see the fun in that. Even if a self built Vue.js web app does some cool things, or looks good on your portfolio. I'll pass.
1. Node.js or package.json or Vue.js or Nuxt.js issues or Ubuntu C library issues
2. Debugging and customizing pre-built CSS frameworks
First of all they're running a very simple blog, a SSG should be more than sufficient for their usecase. If for some reason the engineer in them decides they want to ship their own, which I completely relate to, all these problems come packaged with that decision.
Even then, after browsing their site, it's very barebones, nothing more than a router and a md -> html transformer is needed.
You don't even need a custom CSS framework for whatever this is, all the components on their website are so simple a single CSS file < 300 lines (I'm being very liberal) including media queries should do the trick.
Regarding DNS, in my 15 years of experience building/deploying websites there have been very few cases where setting up DNSs was a pain and that was only when I was using shady webhosts to minimise cost.
Can't comment much on caching, but I remember with Jekyll you can just append `{{ site.time | date: '%s%N' }}` to your asset and lo behold ez cache busting.