The greatest challenges of modern frontend web development aren't CSS, accessibility, or web performance. Leveraging AI agents or mastering JS idio...
For further actions, you may consider blocking this person and/or reporting abuse
I think most javascript code is still written with a disruption mindset, while it should be made with a calmer mindset.
When I do frontend programming, I try to use as less dependencies as possible. Even try to avoid compiling and bundling.
Less code and less cogs in the machine equals less problems.
Thanks for your comment! A calmer, or more stability-focused development mindset would help a lot. Take a Linux Mint distribution with an Xfce desktop manager for example, powered by a multitude of interdependent packages spanning decades of develeopment eras, but still it usaully works well without conflicts.
Avoiding compiling and bundling in web development isn't always the best choice, in my opinion, it depends on the use case. Classic, content-focused front-end websites can still be done with plain HTML, CSS, and vanilla JavaScript (with JSDoc, if we don't want TypeScript transpilation). Content management without relying or WordPress or other opinionated frameworks, thus JAMstack with Hugo, Eleventy, Astro etc. tends to bring a lot of npm dependencies with at, but at least mostly devDependencies that aren't deployed to the frontend, so we can keep calm about most security issues. Once we start with React, Svelte, or Vue for more interactive web apps with complex state management, we're exactly in the situation that inspired this discussion.
A real-life example from my current side project. No more conflicting peer dependencies, everything works now, apart from Tailwind styles in Storybook:
Integrating Astro 5, Storybook 9, Vite 7, and Tailwind 3 🐇🕳️
Ingo Steinke, web developer ・ Aug 8
By releasing hexagonal-masonry-placement I'm now an npm package maintainer myself, so I can add to the dependency and deprecation chaos - or maybe help prevent it?
Seriously, I started factoring out reusable parts of my software and themes into plugins, packages, or template repositories hoping that I can put some fixes and updates in my external or upstream code to propagate it into all dependent or downstream codebases with less repetitive effort and with reduced risk to forget and neglect projects until they will refuse to build locally two years later.
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.
If you never update anything, you'll never have breaking changes!
In all seriousness, I've just now started to run into that problem (both with NPM and other things). I normally just do whatever NPM advises and whatever sounds the least invasive. I gotta start considering the longevity of that gameplan though.
I remember PHP Symfony wasn't much better. Maybe we should learn a "dead" language like COBOL.
You can't have any dependencies if you do everything yourself. It would be so much simpler (but a lot more limiting, of course)
Yeah, but that sounds a little bit like a Roll Safe meme, like "the data can't be wrong if there's no data".
My solution is really a matter of mind-shifting: expect to maintain any code you write forever. Maybe even enjoy it!
The ecosystem will constantly change. Always has. We used to be a community of tinkerers, who could while away our time pruning old dependencies and refactoring things to get a little better at a time... now we've gone the way of society: make a quick buck and move on to the next thing.
The best way to deal with constant deprecations and breaking changes is to keep dependencies minimal, update them regularly in small steps, and document why versions are pinned. Using stable environments like Docker or version managers helps avoid unexpected conflicts. For simple projects, sticking to plain HTML, CSS, and vanilla JavaScript reduces risk. For complex apps, maintain a consistent stack, monitor semantic versioning, and rely on reproducible builds to keep things stable.
I've little knowledge about WordPress but now I want to learn coding.
So, from where I can start???
Can anyone guide me???
Do you want to learn WordPress or do you want to learn coding? WordPress doesn't require much coding to get started, but you can still use coding (HTML, CSS, JavaScript, PHP) to produce better themes or customize existing ones. However, if your want to learn coding, start with the basics. If your want to learn web development, learn HTML, CSS, JavaScript. There are many excellent tutorials and starting points, also here on DEV.