Consuming externally compiled files and maintaining their connection to sources

components: {
  parse: './node_modules/my-lib/src/**/*.jsx',
  load: './node_modules/my-lib/dist/**/*.js',
  css: './node_modules/my-lib/dist/**/*.css'
}

It would help to use already builded components for demo purposes and sources to parse with react-docgen

[mik01aj]

I read your comment 3 times and I still don’t understand what you’re trying to do and what is your problem.

[mik01aj]

Ah, I think that now I finally understand your point.

You want to compile your jsx to js with some tool outside styleguidist (be it webpack, babel or anything), and then you want styleguidist to consume these compiled files instead of compiling them again. Correct?

That’s a fair point, and it should be possible to do it by rewriting some paths for webpack. But on the other hand, I’m not sure if people actually do this often in their projects. In the cases I’ve seen, there is no separation between transpiling and bundling step, and the individual transpiled files are not saved anywhere. So I’m not sure there is a great need for this. What you propose would be cleaner and faster for your project, but I’m not sure it will be that useful for the general public.