next-runtime
Next.js
next-runtime | Next.js | |
---|---|---|
12 | 2,061 | |
605 | 121,256 | |
2.0% | 1.3% | |
9.2 | 10.0 | |
6 days ago | 6 days ago | |
TypeScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
next-runtime
-
5 Ways to Redirect URLs in Next.JS
I say "when it works" because it's not necessarily supported by all hosts. For example, Vercel of course supports it, but Netlify doesn't currently appear to. As for other hosts, you'd need to verify with them, but I'd imagine it varies.
-
My 2023 Year in Review
View on GitHub
-
4./ Client components in static and dynamic routes before Next 13
Note: at the time of writing this, there is a bug in Next (13.4.7). Although Next guarantees that you can use both app router and pages router in the same project, there is a bug that causes a full page reload when you browse from an app route to a pages route or vice versa. This is unfortunate but does not influence our tests.
-
My experience deploying a Next.js application on Netlify (using Next App Router)
So adding an edge function was the only workaround I found. Apparently it's an issue they're working on and I think it should be set as high priority since trailing slashes matter for SEO.
- What is server costs (resources) with Next.js ISR?
-
Next.js rewrites
Here are a great guide on what to use when: https://github.com/netlify/netlify-plugin-nextjs/blob/main/docs/redirects-rewrites.md
-
Netlify: Improved workflow and new role for pricing changes
It also seems like an unconscious acknowledgement that their add-on services (form handling, post-processing, identity, analytics, auth, etc.) are woefully inadequate in some cases and uncompetitive in others. $20/mo for form handling beyond 100 submissions? Okay, maybe. But the feature set is so bare it's laughable. There's minimal to no customization for notification emails, no confirmation emails, and their post-processing for form detection will bring the speed of your build pipeline to its knees on any serious site. On one site turning off post-processing yielded a build time reduction of more than double the actual build time of the site.
Not to mention the fact that by foregoing any concept of a server and forcing everything into some flavor of lambda they've created a scenario where every framework with any such functionality requires open source shepherding to function on their platform[0]. At best they've diluted their initial mission and at worst they've created an unmanageable mess. They can't even make Next.js work on their platform without causing what should issue 404s to return 500s instead[1]. The SEO implications for that are a potential death sentence and that issue has now been open for five months.
I was very optimistic about Netlify at the outset, and it worked great and still continues to work great for our test cases where we've deployed individual LPs. Where the pain seems to start is anything above a thousand pages or more, which is also coincidentally where the stakes start to get higher. I don't know how they could expect anyone at an enterprise or growing business to seriously scrutinize this platform and view it as ideal with that in mind.
[0]: https://github.com/netlify/netlify-plugin-nextjs
-
Next.js measurement: Serve images in next-gen formats even when using next/image
I don't think Netlify supports WebP currently: https://github.com/netlify/netlify-plugin-nextjs/issues/687
- Vercel Welcomes Rich Harris, Creator of Svelte
-
Make a Custom Portfolio Site Generator with StepZen's Developer Publishing Pack
I made the template here using NextJS, because Netlify has a NextJS plugin, which automates the process of using serverless functions. I inserted the call to my StepZen GraphQL endpoint in the pages/api folder to keep sensitive info off the client.
Next.js
-
Essential Tools & Technologies for New Developers
Next.js is a powerful React framework that enables developers to build server-rendered applications, static websites, and more. It's designed for production and provides features like automatic code splitting and optimized prefetching.
-
Tips from open-source: Set a maximum time limit on fetch using Promise.race()
// source: https://github.com/vercel/next.js/blob/canary/packages/next/src/lib/worker.ts#L121C15-L129C16 for (;;) { onActivity() const result = await Promise.race(\[ (this.\_worker as any)\[method\](...args), restartPromise, \]) if (result !== RESTARTED) return result if (onRestart) onRestart(method, args, ++attempts) }
-
Deploying organization repo to Vercel with a hobby plan
https://github.com/vercel/next.js/discussions/27666 One of them said 'renaming folder to uppercase' might cause trouble. git might not recognize case-sensetive changes by default.
-
How to Build Your Own ChatGPT Clone Using React & AWS Bedrock
Next.js has long cemented itself as one of the front runners in the web framework world for JavaScript/TypeScript projects so we’re going to be using that. More specifically we’re going to be using V14 of Next.js which allows us to use some exciting new features like Server Actions and the App Router.
-
Is purging still the hardest problem in computer science?
Web frameworks like Next.js will usually include this feature, but do check that they set the caching headers correctly!
-
Vite vs Nextjs: Which one is right for you?
Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.
-
A brief history of web development. And why your framework doesn't matter
> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.
Would you like to elaborate on that?
In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.
For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/
Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/
Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main
Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/
React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.
Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.
-
System & Database Design (Day 1) - Creating a SaaS Startup in 30 Days
Next.js: For the website and the admin dashboard
-
Runtime environmental variables in Next.js 14
Until the time of writing, there is no official example of how to enable runtime environmental variables in a Dockerized Next.js app, as utilizing unstable_noStore would only dynamically evaluate variables on the server (node.js runtime). There is also an interesting discussion regarding this topic on GitHub.
-
@matstack/remix-adonisjs VS Next.js - a user suggested alternative
2 projects | 24 Apr 2024
next.js is a very popular React framework. remix-adonisjs includes more functionality through the AdonisJS backend ecosystem, and should be easier to self-host and self-manage.
What are some alternatives?
joystick - A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.
vite - Next generation frontend tooling. It's fast!
prepack - A JavaScript bundle optimizer.
Express - Fast, unopinionated, minimalist web framework for node.
services - Real World Micro Services
SvelteKit - web development, streamlined
denoflare - Develop, test, and deploy Cloudflare Workers with Deno.
MERN - ⛔️ DEPRECATED - Boilerplate for getting started with MERN stack
Angular - Deliver web apps with confidence 🚀
ember-render-modifiers - Implements did-insert / did-update / will-destroy modifiers for emberjs/rfcs#415
fastify - Fast and low overhead web framework, for Node.js