Bryce Hill

I ran into this too. I was able to fix it by using webpack's [`resolve.alias`](https://webpack.js.org/configuration/resolve/) feature: ```js resolve: { alias: { 'jquery-ui/datepicker': 'jquery-ui/ui/widgets/datepicker' } } ```

I am seeing something similar when using the iron-multi-selectable.html behavior. From what I could track down, changes (`push` or `splice`) to `selectedValues` are not notifying properly and thus are not...

Thanks for the reply. > using sideEffects you say order doesn't matter I'm curious why this is the case. Is it a technical limitation? For me, the final order doesn't...

@TheLarkInn That's what I thought was happening at first. However, if you take a look at my example [repo](https://github.com/brycehill/webpack-css-order), none of the CSS is eliminated, **but** setting `sideEffects: true` fixes...

Looks like this was fixed in v4.12.1 as described by @sokra, however it broke again in the next minor release (v4.13.0). I pushed an update to my test [repo](https://github.com/brycehill/webpack-css-order) showing...