ladle
pedalboard
Our great sponsors
ladle | pedalboard | |
---|---|---|
9 | 23 | |
2,456 | 18 | |
- | - | |
8.4 | 8.4 | |
14 days ago | about 1 month 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.
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?
pedalboard
-
Take control over your media loading
You can check out some demo examples in this Storybook, and see the code in the pedalboard repo.
-
Get Your TypeScript Coverage Report
Turns out there are tools for that and one of them is called typescript-coverage-report by Alex Canessa and Iām going to give it a try now and implement it in my Pedalboard monorepo.
-
Enhancing a Stylelint plugin (with some TDD love)
Also, all the code mentioned here can be found in the GitHub repository for this plugin. Put your testing helmet on, here we go!
-
Supporting SASS in your TS React project using TSC and esbuild
My Components package currently supports regular plain-old CSS (not that thereās anything wrong with it), and I thought it was a good time to introduce SASS to it, but the package is not a ordinary āWebpack-build-that-s#!t-for-meā. Iām using TSC (TypeScript Compiler) to generate the artifacts - What it means is that TSC is compiling 2 versions of the component, ESM and CJS. Once we have these, weāre taking the ESM outcome and bundling it using esbuild. You can read more about it here, but if to put it visually:
-
Testing Your Stylelint Plugin
In this post I will write a test suite for my @pedalboard/stylelint-plugin-craftsmanlint. We will be using jest-preset-stylelint to help us with that, and as a bonus, Iāll fortify the pluginās TypeScript support.
-
Converting Your React Hook To TypeScript
For reference, below is an image of the Pagination component, and you can find itās code here:
-
Visual Testing Your Components With Chromatic
Disclaimer - Iām going to apply the following steps on my Pedalboard monorepo. Working with monrepos is a bit different, and I will relate to that during the process, but be aware that applying Chromatic on a āsimpleā repo is even simpler.
-
Introducing esbuild To Your Monorepo
I have noticed that although the build process for packages under my āpedalboardā Monorepo creates different artifacts (CJS, ESM and types - you can read about it in more details in my āHybrid NPM package through TypeScript Compiler (TSC)ā post) it does not create a single bundle for the entire package.
-
Visual Regression Testing with Cypress 10
I will attempt to introduce this visual regression testing to my Pagination component from the @pedalboard/components package. So here we go.
-
Giving Jest-Preview a Spin
So letās see how this tool works and what we can do with it. Iām gonna do my experimenting over my Pagination component which resides on the @pedalboard/components package. Letās go!
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]
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
vite - Next generation frontend tooling. It's fast!
testing-react - Testing utilities that allow you to reuse your Storybook stories in your React unit tests!
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]
ESLint - Find and fix problems in your JavaScript code.
js-diary - šIn-browser live coding environment with markdown & JSX support for JavaScript
nx - Smart Monorepos Ā· Fast CI
base web - A React Component library implementing the Base design language
storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.