Ingo Steinke is a Berlin-based senior web developer focusing on front-end web development to create and improve websites and make the web more accessible, sustainable, and user-friendly.
Copyfiles in another example. So, it's been deprecated due to an unsafe dependency to inflight which "is not supported, and leaks memory. Do not use it." Seems the easiest in-place alternative is changing copyfiles to npx. But why on earth hasn't anyone saved their deprecation efforts to submit a fix to copyfiles instead then?
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it.
npm ls inflight
Googling it did not match any documents. It looks like there aren't any great matches for your search. Asking AI produces various alternatives, including including cpx, cpx2, cpy, cpy-cli, ncp and fs.cp(), which at least seem legit at first sight. But again, why not change a widely used peer dependency instead of deprecation and causing a disruptive wave of half-hearted "housekeeping" actionism merge request through hundreds, thousands or probably millions of JavaScript projects?
I also wondered, how serious is the inflight memory leak in practice for small projects with less than a hundred files in total in a handful of directories nested no deeper than three levels? Could we just ignore the warning pragmatically then? In this case, the severity is likely minimal or negligible.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Copyfiles in another example. So, it's been deprecated due to an unsafe dependency to inflight which "is not supported, and leaks memory. Do not use it." Seems the easiest in-place alternative is changing copyfiles to npx. But why on earth hasn't anyone saved their deprecation efforts to submit a fix to copyfiles instead then?
Googling it did not match any documents. It looks like there aren't any great matches for your search. Asking AI produces various alternatives, including including
cpx,cpx2,cpy,cpy-cli,ncpandfs.cp(), which at least seem legit at first sight. But again, why not change a widely used peer dependency instead of deprecation and causing a disruptive wave of half-hearted "housekeeping" actionism merge request through hundreds, thousands or probably millions of JavaScript projects?I also wondered, how serious is the inflight memory leak in practice for small projects with less than a hundred files in total in a handful of directories nested no deeper than three levels? Could we just ignore the warning pragmatically then? In this case, the severity is likely minimal or negligible.