Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Hey, sorry about this. What could we do better?


Not OP but since you're asking: next/image was unusable last time I tried it. I ended up using next-optimized-images, which didn't feel a lot better but was at least usable for my case. I wanted to compile the images at build time instead.

While I'm at it, next/link also had some bonkers defaults such as the link prefetching on view instead of on hover (neither of which could be disabled, either…).

I hope all that is getting some attention soon. If I can offer some frank feedback: I've had an overall positive experience with the framework, but there have been clear quality issues here and there and I'm always concerned when I see a large feature churn without a high amount of attention being put into existing bugs.

I filed three bugs while porting an app over half a year ago (https://github.com/vercel/next.js/issues/20984, https://github.com/vercel/next.js/issues/21474, https://github.com/vercel/next.js/issues/21461). None of them have even been acknowledged by a dev yet. (That last one was a doozy, too; I'm not actually sure it's a nextjs bug)


Maybe this is already fixed in 11.1, but static site generation seemed broken for me with create next app. I had to go in and remove usage of this feature before static build will work.


Are you using `next build`? It should work as expected when `create-next-app`. If not, then would you mind opening up a reproducible issue?


Will do!

The issue is with export, build works https://nextjs.org/docs/advanced-features/static-html-export




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: