styleguide

Describe the bug
The validateArgs method in lib/router/src/utils.ts is using VALIDATION_REGEXP, NUMBER_REGEXP, HEX_REGEXP or COLOR_REGEXP pattern to determine whether the string value is validated or not, but any string which not match those pattern (like something with + prefix or some character that is not in Alphabet) will not be validated and be dropped in future actions.

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

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b

This bug: https://bugs.python.org/issue46175

We need to require super(cls, self) in this case.

I have stories for simple components that work fine. But once I click on a story for a component that uses the next/image component, nothing renders and ladle is broken until reload. Once I clock on a story with next/image the following error occurs in the console:

react.development.js:1309 Uncaught ReferenceError: process is not defined
    at node_modules/next/dist/client/normalize-