2 ms·
Most of those should be "devDependencies", as they're used for build-tooling not for the actual codebase, but I'll be honest I'm right there with you: my major
by girvo 10y ago
Most of those should be "devDependencies", as they're used for build-tooling not for the actual codebase, but I'll be honest I'm right there with you: my major drama with modern front-end dev at the moment is the sheer amount of dependencies that are "required" in a traditional toolset.
That said, leveraging Browserify, Bubleify[0] and Ramda[1] alone can get you pretty far in a seriously maintainable way with modern code, which is super nice: keeps compile times stupid quick and reduces some of the cognitive overhead (and possible maintenance drama) that too many third-party deps introduce.
There's a balance to be struck here, and it's a hard problem, I think.
[0] https://github.com/garthenweb/bubleify https://github.com/garthenweb/bubleify
[1] http://ramdajs.com/0.21.0/index.html http://ramdajs.com/0.21.0/index.html
- xuejie 10y agoI dunno, I think what you are describing is a practical stack, not a minimal one. For me, a minimal stack is just an HTML file(possible with a JS file as well) that loads React and Firebase via CDN, and then relies on browser's shipped ES6 capabilities to write code. But in that sense I might be trolling here since nobody actually does that :)