Only by choice (i.e., if you as a developer add a bunch of packages to Joystick).
I built Joystick to be fairly lightweight on the dependency side (for the exact frustration your joke is pointing at). The core stuff is using long-term stable dependencies. Anything else I built directly into the framework by hand so it would last long-term and not turn into the goose chase that is the JS world.
I refer to it as the "Honda Civic of JavaScript frameworks" for that very reason.
Comments
Now you can have all of the fun of the clusterfuck of modern web development in app form!
(Not criticizing your effort. Red Goose isn’t the problem.)
I'm working on fixing that clusterfuck (which paired with something like Red Goose would restore sanity): https://github.com/cheatcode/joystick.
So now you just have to fix the clusterfuck of Node dependency hell ;).
I haven’t actually looked at your framework or the dependency chain. It’s more of a joke
Only by choice (i.e., if you as a developer add a bunch of packages to Joystick).
I built Joystick to be fairly lightweight on the dependency side (for the exact frustration your joke is pointing at). The core stuff is using long-term stable dependencies. Anything else I built directly into the framework by hand so it would last long-term and not turn into the goose chase that is the JS world.
I refer to it as the "Honda Civic of JavaScript frameworks" for that very reason.