Iñaki Baz Castillo
Iñaki Baz Castillo
HI @lancedikson, let me clarify that yes, I'm used to flags, but just because that is what v1 provides. In fact, I do like the new v2 API :) >...
Hi @lancedikson, thanks for your great response. My usage is exactly this (currently with v1, of course): https://github.com/versatica/mediasoup-client/blob/master/lib/Device.js#L115 Regarding: > browser.satisfies({'opera': '~43', 'chrome': '~41'}) I'm lost here. What does `opera`...
Clear, thanks. So I hope those browser name flags will be documented so I can know whether I should expect just `chrome` or also `chromium`, etc.
Hi @lancedikson, is there any ETA for v2? I'm modernizing my software and it's a proper time to also update its `bowser` version.
Friendly ping :)
Take your time, and thanks :)
Thanks! will check next week and update my project with it. I will let you know how it goes :)
Hi @lancedikson, a side note: I'm checking the API (still learning it). I think it would be extremely useful to have a website to test bowser. I mean, a website...
It would be nice if the docs explain that `satisfies()` may accept many entries and will return true if at least one of them is satisfied. Example: ```js browser.satisfies({ chrome:...
Ok, so I've updated my project to use bowser 2.0.0: https://github.com/versatica/mediasoup-client/blob/master/lib/detectDevice.js#L31 Not super tested yet (just manually in Node doin copy&paste of different browser user agents) but it looks nice....