When will connect-livereload 0.3.0 be used? about grunt-contrib-connect

[vedraan]

If it won't be that soon, some help on how I might manually upgrade to 0.3.0 would be appreciated. I tried running npm update connect-livereload and npm update -g connect-livereload and did a npm list after that, still getting:
├─┬ [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
(stayed at 0.2.0).

I tried:
npm view connect-livereload version
and it returns:
npm http GET https://registry.npmjs.org/connect-livereload
npm http 304 https://registry.npmjs.org/connect-livereload
0.3.0

It just won't update to that version.

[shama]

Thanks, it seems 0.2.0 was pushed as latest so I kept missing it.

[vedraan]

That was fast 👍 Pardon my ignorance when it comes to npm, but when will it be available as an update there?

npm view grunt-contrib-connect
still returns:
dependencies:
{ connect: '~2.7.11',
'connect-livereload': '~0.2.0',
open: '0.0.4' },

Thanks

[robwierzbowski]

👍 to releasing with connect-livereload 3.0. The 40kb bug is biting us too.

Thanks!

[szimek]

@shama Any chances for a new release? This was fixed almost a month ago.

[vedraan]

Still waiting for this one myself. It's a pain... if you have to work on an app that displays even a bigger text article, not to mention larger data sets (hard coded in html).

[szimek]

@vedraan You could replace

"grunt-contrib-connect": "~0.5.0"

with

"grunt-contrib-connect": "gruntjs/grunt-contrib-connect#7fdf7adb0608f6fdb734df58a6b11b07ad55cc9f"

in your Gruntfile.js till the new version is released.

@szimek thanks for the workaround.

When will a release come out?