Definitely! I would love to hear what kind of replacements they had to make:
>As part of our goal to optimize dependencies, we also updated and/or replaced npm packages that were marked as deprecated by their authors – even when they were deeply nested in the dependency tree.
I wonder if they just rewrote some smaller packages themselves, or if they managed to find a maintained alternative for all of them?
I'm super excited about NextJS releases, but there has been a persistent memory leak issue is absolutely killer for larger projects: https://github.com/vercel/next.js/issues/15855. It's so difficult to debug, but dang, it's just brutal to deal with on a daily basis. Hoping some of these dependency reductions help.
6 comments
[ 2.7 ms ] story [ 40.1 ms ] threadGreat to see NextJS putting effort to reduce dependencies.
>As part of our goal to optimize dependencies, we also updated and/or replaced npm packages that were marked as deprecated by their authors – even when they were deeply nested in the dependency tree.
I wonder if they just rewrote some smaller packages themselves, or if they managed to find a maintained alternative for all of them?
Good. Refresh time and compile time feel like biggest drawbacks to Next right now.