Pedro Machado Santa
Pedro Machado Santa
Just added something that can alleviate this issue, added a mechanism that forces a cursor update some time after the user stops typing (and it's debounced): af81b1303f73eb6d3b41c265818e84811b8961a6 It's not ideal,...
> @pedrosanta I have also noticed in my console that I get the console.log('Troubles!', cursor) statement reached quite often. But it still appears that the cursor works just fine... Why...
> Looks like this is a duplicate of #268, but it is not obvious by the title. Yhea @darcyparker, the issue started as the vulnerability report and then shifted focus....
Also, as I state on my comment (https://github.com/gruntjs/grunt-contrib-connect/issues/268#issuecomment-903302596) updating to node `http2` requires a new major version (it's a breaking change on the engine supported versions).
@Krinkle Hello, with the `4.0.0` release and the Node engines/version update (>=16), maybe we can consider, revisit this?
Sure, will post one then, whenever I can. Cheers.
Thank you @wirdehall. LGTM. Will check, run, test, and approve as soon as possible.