Henri d'Orgeval
Henri d'Orgeval
Hi @ravinder455 , v3.0.0 has been published to npm and should resolve your issue. Could you give it a try and provide any feedback?
Hi @ravinder455 , thank you for your feedback. I will fix it asap.
Hi @ravinder455, your last feedback should be solved by v3.0.1 available on npm. Those warning messages should not be emitted any more in the log.
Hi @vsridhargovx , thank you for your feedback. It would be great if you could provide a sample repo that demonstrates your issue, it will help me to fix that...