esbuild-plugin-browserslist
ladle
| esbuild-plugin-browserslist | ladle | |
|---|---|---|
| 1 | 9 | |
| 41 | 2,469 | |
| - | - | |
| 8.5 | 8.1 | |
| 3 days ago | 16 days ago | |
| TypeScript | TypeScript | |
| 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.
esbuild-plugin-browserslist
-
When Vite ignores your Browserslist configuration
(Note: another package can do this, but I have not tested it.)
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?
What are some alternatives?
browserslist-to-esbuild - Get esbuild-compatible targets from a browserlist config or project
storybook - 📓 The UI component explorer. Develop, document, & test React, Vue, Angular, Web Components, Ember, Svelte & more! [Moved to: https://github.com/storybookjs/storybook]
burokku - 🤜 ⍰
vite - Next generation frontend tooling. It's fast!
browserslist - 🦔 Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-preset-env
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]
PostCSS - Transforming styles with JS plugins
js-diary - 📙In-browser live coding environment with markdown & JSX support for JavaScript
base web - A React Component library implementing the Base design language
esbuild - An extremely fast bundler for the web
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.