leerob

42 ms·

1. 481.▲
   by leerob 5y ago

   We're planning to try and release learning material around Rust!
2. 482.▲
   by 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 (li
3. 483.▲
   by leerob 5y ago

   Hey, sorry about this. What could we do better?
4. 484.▲
   by 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@late
5. 485.▲
   by 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 config
6. 486.▲
   by leerob 5y ago

   You can now import npm packages using ES Modules (e.g. "type": "module" in their package.json) with an experimental flag directly in Next.js. Previously, this required extra configuration.
7. 487.▲
   by leerob 5y ago

   Lee from Vercel here! Happy to answer any questions about this release, or Next.js in general. Personally, I'm very excited about the performance improvements we're seeing switching to Rust from Babel/Terser.
8. 488.▲
   Next.js 11.1: ES Modules support, Rust-based tooling, Improved Build Performance(nextjs.org)

   8 points by leerob 5y ago|3 comments
9. 489.▲
   by leerob 5y ago

   > rely on good old HTML, CSS, and vanilla JavaScript. Unfortunately, it's not always that easy. Often times, this same camp will forget about accessibility or other performance indicators like image optimization. Also, native web pl
10. 490.▲
    by leerob 5y ago

    Correct. More information here https://www.smashingmagazine.com/2021/04/incremental-static-...
11. 491.▲
    by leerob 5y ago

    I would encourage you to consider the real experience[1] of your users instead of just a Lighthouse score. Lighthouse is just one tool to understand performance, but prefetching links often leads to a better user experience. If the end perf
12. 492.▲
    by leerob 5y ago

    Related, free template: https://github.com/vercel/nextjs-subscription-payments
13. 493.▲
    by leerob 5y ago

    If you're familiar with Rails, stick with what you know. Often that will be faster than learning a new tool. If you want to diverge and learn something new, you can deploy a full stack application using React/Next.js on the front
14. 494.▲
    by leerob 5y ago

    Hey! Lee from the Next.js team here. We're working on improving the Next.js <> Storybook experience. If you have a specific bug or issue you're hitting, please let me know.
15. 495.▲
    by leerob 5y ago

    One advantage of using Next.js is you can have the same React application for your entire application (marketing pages, dashboard pages, docs, etc) since it supports all rendering types (server rendering, static generation, client-side). It
16. 496.▲
    by leerob 5y ago

    Next.js is built on top of React, FYI! https://nextjs.org
17. 497.▲
    Transform.tools: A Polyglot Web Converter(transform.tools)

    2 points by leerob 5y ago|0 comments
18. 498.▲
    by leerob 5y ago

    "I don't want my server side react lib to do have anything to do with my deploy set up." You can deploy Next.js anywhere that has a Node.js server. It's not dependent on any deployment set up. "Same with how nextjs
19. 499.▲
    by leerob 5y ago

    1. Yes, you can deploy a Vue SPA on the Vercel platform. 2. Yes, you can deploy that same Vue application anywhere else! This applies for static assets (vanilla HTML, single page apps, etc) as well as serverless applications. For example, y
20. 500.▲
    by leerob 5y ago

    Thank you for this! Very helpful. I will work on improving this.
21. 501.▲
    by leerob 5y ago

    Thanks for the feedback. "Our platform enables frontend teams to do their best work" -> Our platform includes frameworks (e.g. Next.js), deployment and hosting (e.g. serverless infrastructure), and collaboration (preview deploy
22. 502.▲
    by leerob 5y ago

    Thank you!
23. 503.▲
    by leerob 5y ago

    That Next.js issue is 5 years old, here's a more recent discussion where we're exploring adding a CSP by default ( https://github.com/vercel/next.js/issues/23993 ). We've also added documentation
24. 504.▲
    by leerob 5y ago

    Hey! Super.so uses Next.js and Vercel under the hood. They are using an unofficial Notion API to convert content to React components, and then ultimately to HTML through Next.js, which is deployed and hosted with Vercel. They also use Verce
25. 505.▲
    by leerob 5y ago

    Clarification – it's actually a fork on the entire VSCode, not just Monaco. This allowed us to add features like locking the editor when others are editing the same file.
26. 506.▲
    by leerob 5y ago

    This is not entirely accurate. First, we are working on build-time image optimization, it just wasn't our first priority ( https://twitter.com/rauchg/status/1402613436081528836 ). Second, the vast majority of N
27. 507.▲
    by leerob 5y ago

    We're working on this! https://twitter.com/rauchg/status/1402613436081528836
28. 508.▲
    by leerob 5y ago

    Next.js Live will have a completely redesigned open-source dev server, which anyone can use to create collaboration features on top – no lock in. This server has been overhauled to run entirely in the browser, using technology like ES Modul
29. 509.▲
    by leerob 5y ago

    Next.js Live uses a modified version of Monaco: https://microsoft.github.io/monaco-editor/
30. 510.▲
    by leerob 5y ago

    While Next.js Live is framework specific (redesigning the Next.js dev server), the collaboration features will eventually be rolled out for the entire Vercel platform!