You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you can figure it out I’d be eternally grateful
gulp 4 upgrade is the biggest issue
On Wed, May 25, 2022 at 09:07 Kurt Sansom ***@***.***> wrote:
I would like to upgrade all the packages to work with Node 16.
Is there a graceful path to do so?
It feels like a slippery slope into dependency hell....
—
Reply to this email directly, view it on GitHub
<#839>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALY2XMG2YE6TFFPPPE653VLYX3HANCNFSM5W5IOIMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
I guess maybe some tips on where to start?
Part of me thinks it would be easier and faster to start from scratch rather than porting, because I would need to a deep dive on how each of the packages are related. I ma not sure what would be a good place to piecemeal it together.
I would like to upgrade all the packages to work with Node 16.
Is there a graceful path to do so?
It feels like a slippery slope into dependency hell....
The text was updated successfully, but these errors were encountered: