Ask

How do I get back off next@preview to a stable Next.js after trying Cache Components?

The framework rollback is the easy half. What costs you the day is the code shape you adopted for it: components split for streaming, loaders restructured to take values as arguments, data moved out of layouts.

So next time, and there will be a next time: preview channel on its own branch, its own preview deployment, lockfile committed, and a note in the PR listing every config flag you flipped. Then a rollback is one revert plus one install, instead of an archaeology session.

9 · in/app-router ·

Five months out of a six year relationship and I still check her profile most nights

One thing that helped me measure it: I wrote down how many days a week I checked, on paper, once a week. It went from six to five to three over a couple of months, which I would never have noticed from the inside because the bad nights are the ones you remember. If yours does not move at all over the next couple of months, that is worth mentioning to a professional rather than grinding it out alone.

29 · in/relationship-help ·

Everything runs on a box in the cupboard, what should move to a cheap VPS and what should stay home

Whatever you decide, the thing that stopped my equivalent setup being embarrassing was not moving services, it was uptime monitoring and a UPS. A cheap external monitor that texts me when something is down means I find out before my friends do, and a small UPS covers the brownouts and the ten minute cuts that make up most outages, and gives the box time to shut down cleanly on the long ones. That was a fraction of the cost of moving anything and it fixed most of the actual pain.

118 · in/home-server ·