upgrade to ps 0.12

[shmish111]

No description provided.

[CLAassistant]

All committers have signed the CLA.

[garyb]

I think something is wrong somewhere if you were forced to make resolutions - maybe some other dependency or dependencies that need updating first - I don't mind making resolutions in projects / apps that aren't going to be depended upon, but having it in a library is going to cause issues for anyone who wants to rely on it too.

[shmish111]

I hate bower so much. ok I can take a look, I just updated everything to latest

[garyb]

I use npm-check-updates to bump everything to the latest version (you can use a flag to run it on bower too) if you don't already know about that. It doesn't help with figuring out where the conflicts are when bower has a meltdown unfortunately, but it's useful to take some of the pain out!

[garyb]

Adding bower as an explicit local dependency doesn't work too well, since it complains if it's not the most up to date version at all times.

[shmish111]

ok I can remove. this was when I was struggling to get yarn run example working but now it does.

[garyb]

Thanks! I'll take more of a look when the dependency stuff is figured out 🙂

[shmish111]

Hmm, the problem is halogen 4.0.0:

Unable to find a suitable version for purescript-web-html, please choose one by typing one of the numbers below:
    1) purescript-web-html#^1.0.0 which resolved to 1.2.0 and is required by purescript-halogen-vdom#3.0.0, purescript-web-clipboard#1.0.0, purescript-web-uievents#1.1.0
    2) purescript-web-html#^2.0.0 which resolved to 2.0.1 and is required by purescript-ace#7.0.0, purescript-web-uievents#2.0.0

How would we proceed with this? Halogen 4.1.0? What should I do (I feel I can ask since you own all these repos 😄 )

[shmish111]

@garyb any update on what you want me to do here? Thanks 👍