TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Next.js 13.4

46 点作者 leerob大约 2 年前

12 条评论

nickisnoble大约 2 年前
Annoying that they hyped up this live keynote, and then it was all previous &#x2F; pre-recorded announcements.<p>I figured with all the other releases, this keynote would show something really big — maybe they should&#x27;ve saved the databases reveal.<p>Instead we get &quot;the thing we announced months ago is out of beta&quot;.<p>Vercel, you&#x27;ve been inconsiderate with my time.
评论 #35818175 未加载
评论 #35818274 未加载
0xblinq大约 2 年前
It&#x27;s astonishing how complex this has become. All the server component stuff is great technologically speaking and if you&#x27;re using React, it&#x27;s a very welcome thing as this will lead in the long term to less bloated applications for end users.<p>But as a developer I just can&#x27;t stand all the complexity and the magic going on. And now a React compiler is on its way too. This is just too much.
评论 #35819396 未加载
评论 #35820771 未加载
评论 #35818331 未加载
reducesuffering大约 2 年前
I&#x27;ve been using the app&#x2F; dir for a couple months now on a side project and I&#x27;m really liking how concisely I can build UI + backend + deployment. Vercel is getting some heat for it&#x27;s pricing, but Next.js is really pushing forward what&#x27;s possible for people without fiddling with DevOps, separate frontend deployment, separate backend deployment, etc. Coming from Django with Create React App, Django Rest Framework, on a VPS, is a relative nightmare compared to Next.<p>For example, in one small file, two functions, you have a reactive UI, styling (Tailwind), backend with database fetching, routing, and deployment handled:<p>async function getPostsFromDb() {<p><pre><code> return await prisma.posts.findMany();</code></pre> }<p>export default async function PostsPage() {<p><pre><code> const posts= await getPostsFromDb(); return ( &lt;main className=&quot;flex min-h-screen flex-col items-center justify-center&quot;&gt; {posts.map((post) =&gt; { return ( &lt;GradientCard key={post.name} title={post.name} &#x2F;&gt; ); })} &lt;&#x2F;main&gt; ); }</code></pre>
评论 #35818441 未加载
评论 #35818372 未加载
poisonborz大约 2 年前
We recently launched a rather complex multi-market B2B booking system for a larger company on it. I was afraid of possible backend limitations and the opinionated structure that often comes with such projects, but it was a complete bliss to be honest. It takes away SO MUCH of the boilerplate with setting up a modern web CRUD project. Community and utils like i18next and NextAuth are top notch as well. Things I might have missed like API middlewares were added in meanwhile. No wonder that it starts to become the standard React framework. Surprised about the negativity here.
pwnstar4ever大约 2 年前
After running Next.js in production for a few years I never want to touch it again. I haven&#x27;t used Vercel, but hosting on AWS I had to patch configurations in dirty ways just to get it to run reliably. I suspect they &quot;locked&quot; things like node config behind the abstraction of Next.js to drive users to their platform where issues are &quot;magically&quot; solved.
评论 #35820005 未加载
kylehotchkiss大约 2 年前
A big benefit of the pages folder is the ability to statically generate content on build time and deploy, then getting the performance benefit of being a static site. Does&#x2F;will the app folder allow for the same static generation capability? Seeing `Is the pages directory going away?` in the release notes to me seems like a hint that the pages directory may be going away.
评论 #35818442 未加载
flashgordon大约 2 年前
Sigh. I&#x27;m a huge fan of next. But am getting a bit worried. As a backend person, Next made it possible for me to build cool pages easily - especially as a static export to be served by my backend of choice. This whole push towards forcing an entire stack worries me. I personally am not building consumer apps so am ok with server side routing and&#x2F;or spas and it feels like every new version the disapproving nod on &quot;no outside backbends&quot; is getting stronger. (As a services developer I personally don&#x27;t find the ROI on the rest of the vercel ecosystem either but I can see why they need to sell the kitchen sink to justify that crazy valuation)
cranglin大约 2 年前
I&#x27;ve been using the App Router beta for a few months on a pre-production project. No major complaints and I can see the vision. However, I (understandably) had a big issue with implementing Algolia Instant Search SSR into it. Fingers-crossed that 3rd party libraries launch support for it soon.
评论 #35818198 未加载
Escapado大约 2 年前
Really hyped about this! I can&#x27;t wait to try it out and watching the CI build as we speak. I am curious however about a few points. From their examples in the blog post it&#x27;s not clear what kind of payloads can be transfered when using server actions. Do they need to be serializable in a specific way? Can I transfer dates? Can they return something (in case I want to validate a form on the server and return an error or a success code)? How does it figure out that the db import will not be bundled into the client? Because it is only used in the function with the &quot;use server&quot; directive? And finally: Can I call &quot;use server&quot; functions in a client component too? In case I want some extra state in there?<p>Maybe there is someone here who knows more!
评论 #35819450 未加载
edgyquant大约 2 年前
I like working with next but some of these changes in 13 kinda suck. Router especially, I inherited a codebase that didn&#x27;t wrap a lot of functionality so hard changes to the way useRouter works from 12 to 13 means I can&#x27;t reasonably upgrade anytime soon.
评论 #35818090 未加载
ivanakcheurov大约 2 年前
Is “API first” principle obsolete nowadays? How can Server Actions allow other clients to use the same backend? That was the whole point of SPAs, mobile clients communicating only over REST&#x2F;GraphQL so that you can add more clients&#x2F;automation&#x2F;consumers later. To do that properly, the endpoint needs to be secured and documented (Swagger or GraphiQL with autogeneration of client libraries in most languages).
vsroy大约 2 年前
Server actions is amazing. I finally will never need to write a single POST&#x2F;GET request, it&#x27;s the perfect RPC.