ouija
storybook
ouija | storybook | |
---|---|---|
1 | 341 | |
12 | 84,776 | |
- | 0.4% | |
0.0 | 10.0 | |
about 1 year ago | 7 days ago | |
TypeScript | TypeScript | |
- | 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.
ouija
-
Snowpack v3.0 - released
Here's a silly Halloween demo built in snowpack - ably-labs/ouija: an online, multiplayer spirit board (github.com) and azure static sites.
storybook
-
What's New in F# 9
I mean, this really depends on what you're looking at.
Here's a sample from the MongoDB client: https://github.com/mongodb/node-mongodb-native/blob/main/src...
Here's a sample from Storybook: https://github.com/storybookjs/storybook/blob/next/code/core...
Here's a sample from Prisma: https://github.com/prisma/prisma/blob/main/packages/client/s...
Here's a sample from Cal.com: https://github.com/calcom/cal.com/blob/main/packages/core/Ev...
It's rather the specific use case that determines the style of the code that's written. In the examples above, there's no need for the teams to choose JavaScript classes and inheritance to model the logic, yet it likely better fits the programming model of those modules.
Look at Nest.js as well: https://github.com/nestjs/nest/blob/master/packages/core/rou...
The whole codebase of Nest.js looks an aweful lot like Spring or ASP.NET (controller syntax) probably because there's a lot of crossover in terms of what APIs need at scale.
It just so happens that most use cases for C# and Java favor applications at a larger scale. Another key difference being object scope and lifecycles -- something that rarely comes into play in the generally single-threaded Node runtime. This being one of the key reasons why dependency injection is a thing in C# and Java land.
-
Storybook: The Workshop for Modern Frontends
Storybook simplifies working on those hard-to-reach spots in your codebase by providing an isolated workspace. It is a separate framework-agnostic app within your repository. You can do everything from developing components to documenting all different component states and showcasing them nicely using MDX with clickable demos and interactively changeable component arguments. You can also test your components within Storybook. Storybook's add-on API allows you to tailor it to your needs.
-
Thoughts on ThoughtWorks Radar 2024
Storybook to help test React components in isolation, utilized heavily for component framework authors
-
Design Systems Explained
Storybook for building component libraries: Provides a sandbox to develop and test UI components in isolation.
-
Show HN: Gomponents, HTML components in pure Go
Not the OP but I think he meant the one at https://storybook.js.org
-
Using Storybook with Angular and Vite 🎨
Storybook is a frontend workshop for building UI components and pages in isolation.
- Rethinking CSS in JS
-
Cleaning & speeding up the JS ecosystem - Journey so far
Through this time, I was at least contributing to various large projects to clean up and improve what I could (e.g. one i've contributed to for a long time is storybook).
-
Good Refactoring vs Bad Refactoring
Write and run tests to ensure your refactored code doesn't break existing functionality. Vitest is a particularly fast, solid, and easy-to-use test runner that requires zero configuration by default. For visual testing, consider using Storybook. React Testing Library is a great set of utilities for testing React components (there are Angular and more variants as well).
- Component Driven Development with Storybook React Native