The core of our code is under "utils"

I like the Node ecosystem because there is no punishment to extracting the contents of /utils to various NPM packages and reusing them across projects.

so... most of your core code is a helper function? I guess that makes... sense?

I am sad-laughing

@homo-lorens I've literally made PR just to export a function

@eo2875 I prefer thematic libraries, but it doesn't really matter; the gist is that you can turn anything into a package without significant additional preparations and publish instantly anytime if you thought of an improvement.

Feel your pain i have 20 Drupal module that floats in jus call wtf is that

tbh I'd rather this than a jumbled mess of spaghetti that tries to reinvent the wheel.

I can see how this can happen. I made a util package that is a class library. Grew out to include some patterns (sets of classes practically always used together) that could exist in there own package. Class autoloading didn't make it heavy on the system though. So in a lot of projects util is the core.

Come think of it; it actually started out as core components in a large integration project. The components where generic enough they could be used in another project so it was split off as a package/dependency.