Documentation

Describe the bug

Hi I can't see any debug webpack output despite the option in the build-storybook --help section:

--debug-webpack     Display final webpack configurations for debugging purposes

It's never displayed and there's no txt log in the output directory either...

❯ npx build-storybook --debug-webpack
info @storybook/react v6.3.4
info 
info => Cleaning out

Hi, I've found the following cheatsheet :

In the README you explain that there must be an edit button in the page and a github button to access the sheet but as you can see it doesn't appear here.

Thx ;)

🚀 Feature

When working with the blog feed, in testing-library's, we would like a way to contain the full article and not just a truncated version of it within the feed since we don't really care about r

Bug Report

Current behavior

I think there's a mismatch of environment variables being read by babel (JSX config) and Styleguidist, causing some issues deeper down.

(I've noticed this was raised before but was closed)

• build.js sets the env to be production here: https://github.com/styleguidist/react-styleguidist/blob/master/src/s

Currently, the width of the logo is fixed at calc(100% / 6) so that the nav links are flush with the search bar:

Unfortunately, this leads to cut-offs in some translations with longer words in the nav bar:

<img width="127

Search Terms

native ecmascript, esm, plugin

Problem

It would be nice to write TypeDoc plugins as ESM modules, using node's new native ESM support

Suggested Solution

typedoc can first try to require() the plugin, then if it gets an ERR_REQUIRE_ESM error, it can import() it instead. This will support both CJS and ESM and will also support CJS transpilers like ts-node.