ladle
Next.js
ladle | Next.js | |
---|---|---|
9 | 2,061 | |
2,477 | 121,256 | |
- | 1.3% | |
8.1 | 10.0 | |
about 1 month ago | 4 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.
ladle
- PSA: Storybook sends telemetry data, opt-in by default
-
Component development with ladle and next/image
After another look at issue #100, we can tell next/image that it should skip the optimization if the component is rendered in Ladle. That is fine, because the bandwidth does not play a big role during the development. With the following code placed inside .ladle/components.tsx ...
-
Storybook 6.5 is out—new workflows and perf improvements
What you guys think of Ladle?
- Ask HN: What are the best alternatives to Storybook
-
Introducing Ladle for React Stories
The new set of web tools is coming and brings huge performance wins. Ladle is using them to provide a significantly faster environment for developing, sharing and testing your React components. Are you ready to give it a try? Also, check our GitHub and give us ⭐.
-
Trying out Ladle - A Storybook Alternative
I notice that changes to the actual story are not reflected in Ladle immediately and require a page refresh. The console spits out that Vite HMR received a “hot update” but nothing happens. Strange. Storybook on the other hand reloads as expected. Unless I’m doing something wrong here, this is a bug that should be taken care of by the Ladle team as soon as they can. Seems that there is an issue already on the matter.
-
Introducing Ladle, a drop-in alternative to Storybook for React components. Based on Vite , instant server start, 4x faster production build, 20x smaller footprint, code-splitting, fast refresh, single dependency & command and no configuration required.
Can you reproduce it with https://stackblitz.com/edit/ladle & create an issue at https://github.com/tajo/ladle/issues?
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?
storybook - 📓 The UI component explorer. Develop, document, & test React, Vue, Angular, Web Components, Ember, Svelte & more! [Moved to: https://github.com/storybookjs/storybook]
vite - Next generation frontend tooling. It's fast!
Express - Fast, unopinionated, minimalist web framework for node.
rollup-plugin-chrome-extension - Bundling Chrome Extensions can be pretty complex. It doesn't have to be. [Moved to: https://github.com/crxjs/chrome-extension-tools]
SvelteKit - web development, streamlined
js-diary - 📙In-browser live coding environment with markdown & JSX support for JavaScript
MERN - ⛔️ DEPRECATED - Boilerplate for getting started with MERN stack
base web - A React Component library implementing the Base design language
Angular - Deliver web apps with confidence 🚀
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.
fastify - Fast and low overhead web framework, for Node.js