One file to configure your Storybook

Everyone benefits when dev tools integrate to unlock new workflows. Storybook is an open source platform for UI development that has hundreds of addons and is used by Airbnb, Lyft, Slack, and Twitter.

I’m excited to share the new simpler, more declarative way to configure Storybook in 5.3. This makes it easier to accomplish common configuration tasks like adding addons and decorators. It also makes it easy for design, visual regression testing and visual review addons to understand your Storybook.

New, clearer configuration files

We renamed Storybook’s configuration file to make it clearer what they do. …

I was drawn to Storybook because it made developing beautiful UIs organized, repeatable, and efficient.

Over the past year I helped maintain Storybook in my spare moments. During that time the project has seen tremendous growth. More and more developers are realizing the benefits of building UI components in isolation!

Growth came with more feature requests and issue reports than I could handle on nights and weekends. I soon realized that accomplishing Storybook’s goals would take dedicated effort.

So I looked for a team that shared my passion for Storybook and would enable me to work on Storybook more. …

Storybook received the “most impactful contribution to the community” award at the React Amsterdam conference ( the biggest react conference in the world, with 1200+ attendees ). Runners up included: ‘bundle-size’, ‘How to GraphQL’ and ‘NativeBase’.

Philipp and I received the award on behalf of the maintainers and gave short speeches. I talked about maintaining Storybook together and how my role has changed over time. I mentioned how happy I am with everything that is happening in the Storybook community; mentioned that the storybook team has big plans for the future.

Philipp spoke about his experience on becoming a maintainer…

Storybook has been known as “React Storybook” since the beginning, but it was rebranded to “Storybook” during the 3.0.0 release.

As described in our roadmap, this change was made to support more UI libraries than just React. And today, with the release of Storybook 3.2, we’re excited to introduce the first of many new “Storybook for <insert framework here>”!
And it’s “Storybook for Vue”!

The choice to start with Vue was an easy one. Vue is gaining crazy traction right now, and it sounded like it would fit rather well technically with Storybook, considering how componentized it is. 👍


I’m a front-end enthusiast and developer, and I love the vibrant javascript tooling ecosystem we’re currently experiencing.

There’s an amazing amount of quality open source software being built and available in the public domain right now. ♥️

So how open is an open source project? Not every project is managed or maintained the same. Some project are small and have just 1 maintainer, some opt for a few gate-keepers or owners.

How you maintain your project is up to you, but we’re opening up Storybook (an OSS project I’m a maintainer of) to be as open as possible.

Intro : why create child processes in NodeJS

When running an application in NodeJS, it’s single threaded, and will only utilise a single core.

Many tasks to a single node process

When performing cpu-intensive or a great number of tasks, you may see this impacting performance, and see runtime/respond-time increase.

If your NodeJS Application has 100% cpu-usage and is taking a long time to complete or slow to respond, this can be improved by dividing the work to be done, and spreading it over multiple processes.

Norbert de Langen

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store