Version 1.0.9 - Breaking Change in Output Format and Semantic Versioning about react-virtualized-auto-sizer

[BlueRexPY]

Try to use this in your webpack config, it worked for me

{
        test: /\.js$/,
        include: [path.resolve(__dirname, 'src'), /node_modules[\/]@?react-virtualized-auto-sizer/],
        use: {
          loader: 'babel-loader',
          options: {
            presets: [['@babel/preset-env', { modules: false }], '@babel/preset-react'],
            plugins: ['@babel/plugin-proposal-class-properties'],
          },
        },
      },

[bvaughn]

Try 1.0.11 (just published). Hopefully it fixes this. If not, please share a repro!

[floriancargoet]

I have the same issue, but it's when I run storybook (which uses webpack & babel).

[bvaughn]

Sorry about the unexpected change in a minor release 🙇🏼 It wasn't intentional, just an oversight.

It would be helpful to have a repro so I could verify if a change on my side fixes this.

I think that using the @babel/plugin-proposal-class-properties plugin might fix this (which I did in 0d2201a).

[rybesh]

Was there a switch from an older version of Babel?

I’m using browserify and importing like this:

AutoSizer = require('react-virtualized-auto-sizer')

The error I get (even with 1.0.11) is:

[Error] Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object.
[Error] Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

Changing to:

AutoSizer = require('react-virtualized-auto-sizer’).default

… fixes the issue.