leerob

24 ms·

1. 331.▲
   by leerob 4y ago

   Yes, the React beta docs use Next.js.
2. 332.▲
   by leerob 4y ago

   This is awesome - nice work! I'm a big of the API Route style integration.
3. 333.▲
   by leerob 4y ago

   AWS offers a set of primitives, not frameworks. These low-level primitives can be combined to build anything you want. Vercel's Build Output API[1] is a level of abstraction higher. Consider Image Optimization. In this post, there&#x27
4. 334.▲
   by leerob 4y ago

   You could swap out React here for another solution (e.g Svelte) and it would mostly read the same. The Build Output API[1] mentioned is how React, Vue, Svelte, and their "metaframeworks" run on Vercel today. [1]: https:/&#x2
5. 335.▲
   by leerob 4y ago

   Sending you an email. I'd like to improve our Python on Vercel docs (lee at vercel.com if anyone else has Python feedback).
6. 336.▲
   by leerob 4y ago

   Will be open-sourcing this soon! Let me know if you're interested (lee at vercel.com).
7. 337.▲
   by leerob 4y ago

   This could turn into a standard across deployment platforms / companies. We'd need to abstract Vercel out (e.g. different folder names) and get feedback from others, but I would be open to it. Having a standard could help drive in
8. 338.▲
   Vercel Build Output API: Infrastructure-as-Filesystem(vercel.com)

   161 points by leerob 4y ago|42 comments
9. 339.▲
   Beginner SvelteKit: A free course for building Svelte web applications(twitter.com)

   3 points by leerob 4y ago|0 comments
10. 340.▲
    by leerob 4y ago

    In the future, yes absolutely! Cloudflare is working on their support for hosting Next.js. And would be happy to chat with you about your solution.
11. 341.▲
    by leerob 4y ago

    Hey there, sorry about this experience. Would love to help investigate – want to send me an email (lee at vercel dot com)?
12. 342.▲
    by leerob 4y ago

    Here's an example with SvelteKit[1]. You can put a middleware.ts (or.js) in the root folder of any framework and it will work. We also have examples for using Edge API Routes, which work with any framework[2]. [1]: https://g
13. 343.▲
    Vercel Edge Middleware: Dynamic at the speed of static(vercel.com)

    113 points by leerob 4y ago|48 comments
14. 344.▲
    Next.js 12.2: Middleware, On-Demand ISR, Experimental Edge SSR and API Routes(nextjs.org)

    47 points by leerob 4y ago|13 comments
15. 345.▲
    Turborepo 1.3(turborepo.org)

    6 points by leerob 4y ago|0 comments
16. 346.▲
    by leerob 4y ago

    Swing and a miss on this one, haha
17. 347.▲
    What makes a great developer experience?(leerob.io)

    13 points by leerob 4y ago|4 comments
18. 348.▲
    by leerob 4y ago

    We also have Postgres database providers in our marketplace like Supabase. Have you tried them before?
19. 349.▲
    by leerob 4y ago

    This is a great option :)
20. 350.▲
    by leerob 4y ago

    Yeah, we have quite a few customers who host their frontend on Vercel and their backend on Heroku.
21. 351.▲
    by leerob 4y ago

    Thanks, I've updated the post!
22. 352.▲
    by leerob 4y ago

    I prefer to explicitly call it out, even if I believe this post is a fair summary of the story of Heroku. Are there points you disagree with or that are inaccurate?
23. 353.▲
    by leerob 4y ago

    [Author here] I did not know that! Thanks for sharing, will add it. I started using Heroku in 2012 for context, pre in-browser IDE form.
24. 354.▲
    The Story of Heroku(leerob.io)

    129 points by leerob 4y ago|35 comments
25. 355.▲
    by leerob 4y ago

    We've been very intentional about incremental adoption and reducing the number of breaking changes, as well as giving folks codemods when they upgrade and providing escape hatches. For example, when upgrading to Next.js 12, which turne
26. 356.▲
    by leerob 4y ago

    Fixed!
27. 357.▲
    by leerob 4y ago

    The current working idea is that you wouldn't use index.js. There are Layout Components and Page Components, both explicitly defined by `layout.js` and `page.js`. We are open to other opinions here, though. Others have shared similar s
28. 358.▲
    by leerob 4y ago

    Part of the thinking behind `app/` is that each section of your application can become its own app. Separate layouts, separate data fetching, and more. `pages/` was mapped very linearly to routes – `pages/index.js` was the in
29. 359.▲
    by leerob 4y ago

    Yes, I believe you are correct. This would be a good example to add as the updates to `next/router ` start to materialize.
30. 360.▲
    by leerob 4y ago

    Static isn't going anywhere. In my opinion, one the best parts about Next.js is you can blend static with dynamic, on a per-page basis. Your landing page can be completely static + periodically updated in the background (i.e. ISR) and