5.0.0-beta.9: JSS Dependencies Complain About "Unknown [Babel] Plugin" When Omitting include Properties in Rules

[kohlmannj]

I've prepared a reduced test case repo for this issue.

• Reproducible demo: nytpi/styleguidist-5.0.0-beta-babel-issues-rtc
• Style guide config: styleguide.config.js
• Webpack: 2.2.1
• OS X 10.11.6

When using a custom Webpack config with rules that omit include properties, in particular for the JavaScript source files rule, it seems that several of Styleguidist's JSS dependencies cannot find certain Babel plugins.

Assumed workaround: add include properties to rules configs. Would be nice to omit include if possible, though.

Please let me know if there are other details I've failed to provide! Thanks!

[sapegin]

There are two things:

1. You should either include your code or exclude node_modules in your babel-loader. Otherwise you will have problems like this (see also warning about Lodash — it will just slow down your build in the best case).
2. JSS shouldn’t publish .babelrc to npm, I’ll make an issue there.

[kohlmannj]

@sapegin Thanks for the speedy reply!

Re (1): I suspect I'm misunderstanding the Webpack best practice for building projects with external non-ES5 dependencies. I'll look further into this and see what's best for my real project; thanks for confirming this problem for me.

Re (2): oh good, glad this particular issue wasn't just my babel-loader rule alone.

[sapegin]

1. If you have something that needs transpiling in node_modules it complicates config a bit ;-) I list of all this dependencies and my own code in include of babel-loader. Like this.

[sapegin]

(I also highly recommend @bebraw’s book on Webpack :—)

[sapegin]

JSS PR for reference: cssinjs/jss#415

[kohlmannj]

Closing this issue since (1) I have obvious ideas about a workaround, really by way of config best practices (2) the JSS PR has been filed. Thanks again @sapegin, super helpful!