from Hacker News

Next.js 11.1

by wener on 8/12/21, 12:02 PM with 30 comments

  • by Eric_WVGG on 8/12/21, 3:01 PM

    "these changes in front-end frameworks makes everything slower" everyone starts screaming

    "these changes in front-end frameworks makes everything bonkers faster" chirps

    kudos to the Next team doing the good work

  • by pull_my_finger on 8/12/21, 4:53 PM

    I'm really not a fan of the next/image component at all. It's so unintuitive to use.
  • by Thomaschaaf on 8/12/21, 7:13 PM

    Why was SWC chosen instead of esbuild? I see esbuild in a lot more places.

    Also with the developer of SWC joining next.js will the non-open-source parts (STC)[1] be released?

    [1]: https://stc.dudy.dev/

  • by ostenning on 8/12/21, 8:49 PM

    I personally would love to see better i18n routing in nextjs. Supporting translated routes while routing to the same page, e.g: /project, /projekt and /projet for en, de and fr
  • by bilater on 8/12/21, 3:06 PM

    Noob question but when they say ES Modules support will be integrated does that mean for the server side stuff / serverless functions?
  • by kylegalbraith on 8/12/21, 2:51 PM

    I'm a fan of the improvements made to next/image!
  • by presentation on 8/12/21, 2:57 PM

    Hm, does the switch to SWC impact babel config support?
  • by adursun on 8/12/21, 2:46 PM

    Next.js is getting better every day!