Live data from Hacker News

Next.js 13

nextjs.org

31–40 of 106 posts

Re: Next.js 13

#31
post #13

Earlier quoted context omitted.

You should still be able to use alt="" to indicate that it is "decorative" and not meaningful imagery for a visually-impaired user.

That's like the difference between null and undefined.

If you have no alt attribute, then screen readers read the URL!

Empty strings are the way to go for decorative images

Re: Next.js 13

#32

What i am still missing is the possibility to deploy next.js to a serverless platform where files have to be stored in S3 or Google Cloud Storage. Had anybody success to get it working, without loosing ISR functionality?

Where are you struggling? Just `next build && next export` and your static site is compiled to the /out folder which you can subsequently push to S3 or Google Cloud Storage.

No idea what ISR stands for.

Re: Next.js 13

#33
I find the data fetching example extremely confusing…

1. Where does this "use" comes from ? It is not present in the official React API reference : https://reactjs.org/docs/react-api.html

2. It says that the value is not serialized, but what if Page is rendered client side and I want getData to always be executed server side (for example, it may contains secret API key, or make a database call) ?

3. getData is async, so what happens to name if the promise is not yet resolved ?

Re: Next.js 13

#34

Their tutorial is incredible, everyone should take a lesson from Vercel on this: https://nextjs.org/learn/foundations/from-react-to-nextjs/ge... Tell me: 1. What I need to know to understand this documentation 2. The before state (plain React.js) 3. The after state (Next.js) I'm fucking sold, I'm going to use Next.js just based on how well written this documentation is.

Their tutorial is fine, but personally I'd much rather just see a GitHub repo of a project that covers all the basics (eg. a CRUD app).

Why not both: https://github.com/vercel/next.js/tree/canary/examples

Re: Next.js 13

#35

Their tutorial is incredible, everyone should take a lesson from Vercel on this: https://nextjs.org/learn/foundations/from-react-to-nextjs/ge... Tell me: 1. What I need to know to understand this documentation 2. The before state (plain React.js) 3. The after state (Next.js) I'm fucking sold, I'm going to use Next.js just based on how well written this documentation is.

> I'm going to use Next.js just based on how well written this documentation is.

I Understand the euphoria, but this is a pretty bad take.

Re: Next.js 13

#36
post #33

I find the data fetching example extremely confusing… 1. Where does this "use" comes from ? It is not present in the official React API reference : https://reactjs.org/docs/react-api.html 2. It says that the value is not serialized, but what if Page is rendered client side and I want getData to always be executed server side (for example, it may contains secret API key, or make a database call) ? 3. getData is async,…

it's a new "hook", https://vived.io/new-hook-is-coming-to-react-frontend-weekly... https://github.com/reactjs/rfcs/pull/229 contain some discussion

Re: Next.js 13

#37

What i am still missing is the possibility to deploy next.js to a serverless platform where files have to be stored in S3 or Google Cloud Storage. Had anybody success to get it working, without loosing ISR functionality?

Where are you struggling? Just `next build && next export` and your static site is compiled to the /out folder which you can subsequently push to S3 or Google Cloud Storage. No idea what ISR stands for.

Incremental Static Regeneration. Next.js allows you to create or update static pages after you’ve built your site but stores them on the filesystem, which in a serverless environment does not exist.

Re: Next.js 13

#39

Earlier quoted context omitted.

That's like the difference between null and undefined.

If you have no alt attribute, then screen readers read the URL! Empty strings are the way to go for decorative images

[deleted]

Re: Next.js 13

#40
post #20

The next-gen bundler rewrites are getting insane, just as things were consolidating in the other parts of JS. We now have: - EsBuild - SWC (also written by someone who works at Vercel) - TurboPack - Vite (rollup) - Parcel - Rome I've noticed in the javascript ecosystem there is much less convergence than in other languages. Everyone wants a flag in the ground.

Vite is built on esbuild and Rollup, but there’s nothing tying it to either. In theory with the evolving ecosystem, it can swap whatever it wants to use internally and still provide a consistent experience.
Post reply on HN