Add Express.js support

What we do under the hood is emitting a new asset from webpack at carte-blanche/index.html. (or whatever you specify in the dest option) This means that if you’re using express.js for routing, users will never find the Carte Blanche because express.js sends back a 404.

We should be exposing an easy-to-use route which redirects to Carte Blanche. I’ve never done this before, so maybe there’s a better way, but this seems like the nicest solution at the moment:

import { carteBlancheRoute } from 'carte-blanche';
/* … */
app.get('/carte-blanche/', carteBlancheRoute);

[ericclemmons]

Hi! It sounds like this overlaps with the request I have:

• We have a component playground as part of our application under /components, which is part of our application’s routes.
• I’ll be testing out this project this week (better to back the community than a private project, IMO!), but would want to “embed” it within the app.

It sounds like this is possible, based on the internals I took a cursory look at.

Is this issue for the same feature?

[mxstbr]

Done with v0.2! 🎉