v1.9.0 bump

[benmosher]

There are more things I had hoped to complete during this release, but it's been a while so probably best to ship what's done, first.

• get the old once-over and signoff from @jfmengels
• tag
• publish to next
• give it a day
• move to latest

officially broken, can't release as-is

[jfmengels]

Let's do this :)

[benmosher]

FYI @lukeapage, @le0nik, @josh: just published 1.9.0 to next tag on npm. Let me know if you have issues.

[benmosher]

Once this goes green I'll move to master, but 1.9.0 is officially broken, so it will never move to next 😓 .

@lukeapage and @le0nik I need you two to provide feedback on my changes in e044e37, ideally in the form of additional tests.

[jfmengels]

What are the problems?

[lukeapage]

@benmosher a quick review of it looks good, i can try it out on our repo soon.

[lukeapage]

confirmed, it still works nicely for my use case (also the one I added a test for)

[benmosher]

@jfmengels the new custom resolver stuff tries to load actual Webpack instead of the Webpack resolver plugin, due to the original precedence order.

Doesn't show up in tests because Webpack isn't installed, but it happened immediately when I tried it in my actual project. 😅