Post

Yesterday I built a Go web app that served an embedded static next.js site for the UI. It was glorious. Today I tried to run the nextjs build again and got a hundred npm errors. Computers were a mistake.

1 repost133 likes

Only 100 npm errors when dealing with nextjs? Consider yourself lucky 🙌 all jokes aside, I feel like most of nextjs ideas are very good in theory but from my experience in practice there is a lot of pain and suffering 😮‍💨

This gave me flash backs of setting up a a db in mariadb and my emulator working perfectly then restarting my computer only for mariadb to have become corrupt and throw a bunch of errors over some bug that had existed for years. I was not happy having to set everything up again. But yeah, computers✨

If you do C:\> npm ci <ret> Before C:\> npm run build <ret> The ci command will install the exact versions from the auto created package–lock.Json without updating anything. Then the Build command will build the same as before. Effectively the ci command locks your libraries.