Minimal SSR fix.

[microbit-matt-hillsdon]

See e.g. webpack/webpack#6522 /
webpack/webpack#5843
and the docs at
https://webpack.js.org/configuration/output/#outputglobalobject

This was broken by the Webpack 4 upgrade in #273.
This fix effectively reinstates Webpack 3 behaviour, using this rather than assuming window.
In node it'll be using module.exports anyway, we just need not to explode because of window + strict mode.

Note the component still doesn't really support SSR, but
its calls to Browser APIs are in componentDidMount and similar
so are delayed until client side.

Todos pending approval of approach

• package.json:version has been updated with npm version patch (or major/minor as appropriate)
• @brainhubeu/react-carousel version has been updated in docs-www/package.json to the same which is in package.json:version

[piotr-s-brainhub]

@microbit-matt-hillsdon

thanks for this PR but I don't understand what is the benefit as it doesn't provide SSR

[microbit-matt-hillsdon]

@microbit-matt-hillsdon

thanks for this PR but I don't understand what is the benefit as it doesn't provide SSR

@piotr-s-brainhub, thanks for taking a look.

In 1.12.0 I was able to use this component just like any other in my Gatsby project. It didn't render anything until after componentDidMount, but that was acceptable to me for a dynamic component like this. I could wrap it to display a placeholder or just accept that it would render nothing server side. I'd say at this point it was SSR-friendly, even if it didn't render until client side.

In 1.12.1 (after #273), this was no longer possible as the module wrapper accessed window at import time (due to webpack v4 UMD module default behaviour changes) so my Gatsby build failed. From the variety of workarounds suggested on #287, I guess I'm not the only one that cares about this configuration.

If I find time in future, I would also be interested looking at how hard it would be to render something server side too, but for now this simple fix will get users back to where they were with 1.12.0.

I'd love to see this merged to make the code SSR-friendly again.

[piotr-s-brainhub]

@microbit-matt-hillsdon

I opened #352 instead as only the main repo allows building testing environment