Webpack example is referencing undefined values

Looking at https://github.com/linkedin/css-blocks/tree/master/packages/@css-blocks/webpack

The typical JSX end-to-end integration with webpack looks like this: is referencing

const CssBlockAnalyzer = new CssBlocks.Analyzer(paths.appIndexJs, jsxCompilationOptions);

where both paths and jsxCompilationOptions are undefined. jsxCompilationOptions is also referenced later in the plugin inclusion definition.

It would be awesome if you could provide a complete end to end example of how to integrate with Webpack or add example values for those properties.

[chriseppstein]

@bitttttten We want to support projects that don’t use typescript. We thought that https://github.com/linkedin/css-blocks/commit/97cd2e46d0c08dbc05b2610ccfa4f4de1793de20 addressed that aspect. Please file a separate issue about typescript being required with details and we’ll get it sorted out.

regarding the state of the documentation, we’re a brand new project, and so our documentation is certain to miss use cases or be incomplete. That’s why this is a developer preview release and not a 1.0. Please help us improve by providing constructive suggestions. Thanks.

[chriseppstein]

Hi @nonken, sorry the example isn’t correct. We’ll tidy that up.

In the meantime, you can look at how our website is configured or at one of these minimal apps:

• https://github.com/matthiaskern/css-blocks-hello-world
• https://github.com/montogeek/css-blocks-webpack-3