HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
carteb
carte-blanche
JavaScript2016–2016
carteb / carte-blanche · Archived

carte-blanche

An isolated development space with integrated fuzz testing for your components. See them individually, explore them in different states and quickly and confidently develop them.

3Distinct people
3Mentions
0Explicit recommenders
1.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An isolated development space with integrated fuzz testing for your components. See them individually, explore them in different states and quickly and confidently develop them.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2016-06-03 09:51:45 UTC to 2016-06-03 15:35:55 UTC.

012016-06-03 09:00:00 UTC to 2016-06-03 10:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 3, 09:002016-06-03 10:00:00 UTC to 2016-06-03 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-03 11:00:00 UTC to 2016-06-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-03 12:00:00 UTC to 2016-06-03 13:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 3, 12:002016-06-03 13:00:00 UTC to 2016-06-03 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-03 14:00:00 UTC to 2016-06-03 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-03 15:00:00 UTC to 2016-06-03 16:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 3, 15:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 3, 09:002016-06-03 09:00:00 UTC2016-06-03 10:00:00 UTC110
Jun 3, 10:002016-06-03 10:00:00 UTC2016-06-03 11:00:00 UTC000
Jun 3, 11:002016-06-03 11:00:00 UTC2016-06-03 12:00:00 UTC000
Jun 3, 12:002016-06-03 12:00:00 UTC2016-06-03 13:00:00 UTC101
Jun 3, 13:002016-06-03 13:00:00 UTC2016-06-03 14:00:00 UTC000
Jun 3, 14:002016-06-03 14:00:00 UTC2016-06-03 15:00:00 UTC000
Jun 3, 15:002016-06-03 15:00:00 UTC2016-06-03 16:00:00 UTC101

What Hacker News says

3 sources
I have met skidding last February when this was project was in its early stages. We walked through Cosmos and it definitely was an inspiration to Carte blanche. Skidding even helped us to design the initial props form: https://github.com/carteb/carte-blanche/issues/47 Cosmos in my opinion is a fantastic tool and covers even some areas we haven't touch yet, but planning to do soon like injecting/manipulating the internal state of a component. While there a many more differences these are probably the most interesting ones: - The core of Carte blanche is a Webpack plugin. By hooking into the main compilation of Webpack Carte blanche can identify your components and list them in an application living within your running server on different URL path. The coolest part from my perspective is that we inherit all your webpack settings by default.
Read the rest
No need to configure your loaders. Cosmos in comparison is a separate app. - In Cosmos your need to write your examples by hand. Carte blanche reads out your propTypes/Flow types and allows us to generate a form input for each of your properties including nested structures like a person object containing an avatarUrl, firstName & lastName. This approach allowed us to create some kind of UI fuzz-testing feature in the interface. While I believe that it's important to focus your efforts designing/developing for the most likely cases it's also relevant to cover edge-cases. Fuzz-testing is a great way to discover them. I hope this help. Let me know if you any other questions :)
In Carte Blanche – isolated development space with integrated fuzz testing

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.