I’ve been writing JS my entire career and never wrote a package.json file. I’m not sure what tool would even use it.
But then again, I’m a happy, sane person who only writes client-side JS.
But then again, I’m a happy, sane person who only writes client-side JS.
I've never written backend javascript. I've used and fought all the tools mentioned
what happens if your project has tens or even hundreds files, how do you get that to client without any sort of bundler?
But first, I try to avoid using JavaScript in the first place when not strictly necessary. This means server-side rendering as much as possible rather than doing the glacial "load an almost entirely blank page, load giant JS blobs, then load the page content via AJAX and hope that nothing goes wrong in that process, sorry slow connection users, non-standard browser users, and search engine bots" approach which thankfully is finally starting to see some pushback.
> I’ve been writing JS my entire career and never wrote a package.json
And you replied:
> how do you get that to client without any sort of bundler?
Please connect the dots for me.