Browser-sync: express 2.x series is deprecated && connect 1.x series is deprecated warnings

[matt3224]

warning browser-sync > browser-sync-ui > weinre > [email protected]: express 2.x series is deprecated
warning browser-sync > browser-sync-ui > weinre > express > [email protected]: connect 1.x series is deprecated

Just FYI

[EvtK]

+1

browsing for the same thing, ended up here :).

Please update, thanks.

[garbinmarcelo]

+1

[gleip]

+1

[sengemann]

+1

[duxy2002]

+1

[ghost]

+1

[RomkaLTU]

+1

[raphaelokon]

This is also breaking Node v4
browser-sync depends on browser-sync-ui "0.6.3" which in turn depends on
weinre which in turn depends on
the deprecated express listed above which in turn depends on
the deprecated connect listed above
which includes mime ">= 0.0.1"
which in turn breaks for all Node < v6 as it resolves to [email protected]
which dropped support for Node https://github.com/broofa/node-mime#version-2-notes
/cc @bmuenzenmeyer

[harshitkumar31]

+1

[Hatko]

+1

[spencerbeggs]

+1

[Sinequanonh]

+1

[EugeneAndrievsky]

+1

[mehfuzh]

+1

[ben-coates]

+1

[katerberg]

Is there an update on when this will be fixed?

[shakyShane]

Hi all!

The 'fix' here is to remove weinre altogether - it's old & probably no-one uses it anyway!

That would make it a new major version, which is not an issue, but any code related to the UI that contains weinre refs needs updating too, meaning it's a good few hours work.

[matt3224]

@shakyShane eta?

[phamdt]

does someone want to volunteer a PR?

[shakyShane]

@matt3224 @phamdt within the next 2 days :)

[shakyShane]

released as [email protected]

There was no API related to weinre, so I'm releasing as a minor update - it removes functionality, but cannot 'break' anyones tools/projects/builds that rely on 2.x

[simonua]

You, sir, are awesome! I am updating this dependency of mine right now to start testing it. Thank you very much, @shakyShane!

[simonua]

Tested great. Released our internal, consuming package last night. Thanks again, @shakyShane! Happy holidays!

[ckken]

why kill my weinre?

[luwes]

does anyone know another way than Weinre to debug Google Chrome on iOS?

[quisse]

Using weinre standalone in combination with ngrok can do great things.
https://www.undefinednull.com/2015/03/17/remote-debugging-localhost-with-weinre/

[JodiWarren]

does anyone know another way than Weinre to debug Google Chrome on iOS?

@luwes If it's any help, you shouldn't be getting rendering differences between Chrome and Safari on iOS. Due to Apple's restrictions, Chrome is using exactly the same rendering engine as Safari.

Safari on iOS can be debugged with Safari desktop, so that might suffice for your needs.

If you do need to debug it on an actual device, Browserstack offers Chrome iOS as a platform.

I know it's not a 1:1 replacement, but hopefully some of that can help.

[kilgarenone]

How do you guys do remote debugging now that 'weinre' is gone?

[surunzi]

I wrote a replacement for weinre, using the lastest chrome devtools frontend. Check it out: https://github.com/liriliri/chii

[Mr-Chilly]

@surunzi thanks a trillion, it's better, faster, and the easiest option for remote debugging awkward devices!