Hi there @UCFG3SDFV, are there any errors in the browser console?

I think sometimes bumping a version can cause issues with how some of the resources are loaded

If you are using shadow-cljs, try clearing the .shadow-cljs directory

My e2e tests seem to work on osx on node

No error, it's literally a blank window with a blank console. I didn't bump the version nor change the code, simply executing it from osx. I blew up .shadow-cljsas well as .cpcachejust in case, didn't change anything 😞

Okay, good to know. What version are you using?

Initially 0.18.1, same with 0.19.2

osx 12.1 (M1 Max)

The CLI uses open LINKright? Any reason p/openhas to use Chrome?

If you pass in :portal.launcher/app false, it should open in your default browser

Nope, it opens Chrome whereas my default browser is Brave. And indeed, when I was reading the code, albeit quickly I confess, it was about (find-chome-bin)or something like that :thinking_face:

And the CLI works because it relies on calling open LINK in the shell which does just that, open the default browser At least that was my quick conclusion

It seems to reach this path https://github.com/djblue/portal/blob/master/src/portal/runtime/browser.cljc#L97

True, but if you pass in the option, the if will kick you to https://github.com/djblue/portal/blob/master/src/portal/runtime/browser.cljc#L89.

Right, on Linux passing false resulted in a tab being opened in my current (and default browser), true But now on osx nothing happens 😕 It must be something silly

What node version are you using?

I'm running v16.13.0 of node

Is (.-platform js/process) for m1 macs still "darwin" ?

Yes, that was my hunch too but it's still "darwin"`

Oh wait

An earlier node version works

But v17.3.0 doesn't

Okay, I'll try that version and see what happens :thumbsup:

I knew it was something silly! But I've been installing stuff whole day, i didn't consider node could misbehave on something like that Thanks for your help 👌

Ohh, I see the issue. The url being generated is http://::1:49587?fa260c66-f2c4-453c-8df5-9eea6db5262c . Not sure why the node http server is returning ::1 instead of 127.0.0.1

Ah yes, makes sense 🙂

https://github.com/djblue/portal/commit/5cdba58aa246ac8cae434d772f870a7678df09fc will fix the issue in the next release

Thanks again for the bug report!

And thanks for the fix!