5 ms·

Next.js 11.1

• awezsdg 5y ago
  FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS! FUCK MASKERS!
• adursun 5y ago
  Next.js is getting better every day!
• kylegalbraith 5y ago
  I'm a fan of the improvements made to next/image!
• presentation 5y ago
  Hm, does the switch to SWC impact babel config support?
  • leerob 5y ago
    With 11.1, SWC support is still experimental (we haven't enabled it by default). In the next release when this becomes stable (and replaces Babel), we will provide more guidance and examples. If you have an existing custom Babel configuration, you'll still be able to de-optimize and "eject" from SWC and continue using Babel. This ensures we don't break existing applications and make it easier to incrementally adopt these new performance improvements.
• Eric_WVGG 5y ago
  "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
  • leerob 5y ago
    Thank you! We strongly believe Rust is the future of JS tooling[1] and will be investing heavily in this ecosystem. It's been in the works for awhile[2] and I'm happy to start seeing these changes land in Next.js. `npm i next@latest` for perf improvements every time is the goal! [1]: https://twitter.com/rauchg/status/1417861178290851842 https://twitter.com/rauchg/status/1417861178290851842 [2]: https://twitter.com/rauchg/status/979525321882984448 https://twitter.com/rauchg/status/979525321882984448
    • dmitryminkovsky 5y ago
      Hadn’t heard of SWC, only esbuild. Why did your team choose SWC/rust over esbuild/go? This: https://mobile.twitter.com/rauchg/status/979525321882984448 https://mobile.twitter.com/rauchg/status/979525321882984448 ? Thanks a lot for Next.js and the Vercel platform. Both are great.
      • leerob 5y ago
        We chose SWC over esbuild for a few reasons: 1. SWC is designed to be extensible. We can use it as a crate with no forks! [1] 2. We love the Rust ecosystem. Stellar community & WASM support. Excellent long-term performance prospects (like total control over memory management). [1]: https://github.com/padmaia/next.js/blob/cf1d081c5b2f55085cebc9509b13c67c4bf34bd1/packages/next/build/swc/src/lib.rs#L40-L46 https://github.com/padmaia/next.js/blob/cf1d081c5b2f55085ceb...
        • wdb 5y ago
          Seems reasonable decision but for me it increases the barrier to contribute. I already learning Go to contribute to some projects
• bilater 5y ago
  Noob question but when they say ES Modules support will be integrated does that mean for the server side stuff / serverless functions?
• pull_my_finger 5y ago
  I'm really not a fan of the next/image component at all. It's so unintuitive to use.
  • leerob 5y ago
    Hey, sorry about this. What could we do better?
    • ozten 5y ago
      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.
      • leerob 5y ago
        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?
        • ozten 5y ago
          Will do! The issue is with export, build works https://nextjs.org/docs/advanced-features/static-html-export https://nextjs.org/docs/advanced-features/static-html-export
    • scrollaway 5y ago
      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/20984, https://github.com/vercel/next.js/issues/21474 https://github.com/vercel/next.js/issues/21474, https://github.com/vercel/next.js/issues/21461 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)
• Thomaschaaf 5y ago
  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/ https://stc.dudy.dev/
  • cercatrova 5y ago
    Because they "strongly believe Rust is the future of JS tooling." I'd agree honestly, I like Rust a lot more than Go. But that's a debate for another time. https://news.ycombinator.com/item?id=28157256 https://news.ycombinator.com/item?id=28157256
  • bern4444 5y ago
    My cursory knowledge is Go is best for distributed services and things that heavily involve the network. Rust is better for memory based operations due to its safety and speed.
    • rk06 5y ago
      But that's just total BS unless they are directly writing rust code. If you are using tools like swc or esbuild, then you need to evaluate tool itself, not the language it was written in.
      • TheCoelacanth 5y ago
        They hired one of the SWC devs, so they are directly writing rust code.
      • bern4444 5y ago
        Of course you should care about the language the tool was written in. As another example, 1Password is redoing their mac app in electron. Many are upset about this and concerned it will lead to worse performance. Solely because of the technology being used. Similarly here, evaluating esbuild vs swc inherently involves comparing their capabilities, benefits, potential etc. A lot of that is informed by the language its written in.
• ostenning 5y ago
  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