Future / EOL discussion #691
Description
Current state
There is a modernization available (#674) that
- cleans up the current code (removes unused code, cleans up internal structure, adds TS types)
- offers a new modern package with a new structure that helps reducing code (esp. when tree shaking) with multiple entry points and a cleaner API
Dependencies like fetch are now available by default.
Date utils should be moved to the Temporal API (when widely available).
Discussion
of keeping and maintaining this repository:
Pros
- with TS types (especially predicates) the utility functions can be helpful
- it's always good to have a collection of re-usable helpers/functions
Cons
- adding an extra dependency
- and many utilities are really simple
- managing external dependencies (like Google cloud in here) is not really useful
IMHO we should keep this repo for now, but stick to simplicity and ideally remove any external dependencies (i.e. all the cloud deps) to reduce the size and possible security problems. As far as the usage analysis revealed, the cloud helper functions are not used (on a side note: they are duplicated in some projects that access clouds).
As suggested in the modernization, we could use a mono repo to actually host all our utils in this repo (but this is open to discussion).
We could also just maintain a simple collection of utility functions.
If there is no future, for this repo i suggest looking at https://github.com/toss/es-toolkit that offers utility functions as well.
And as mentioned before, many utility functions are very simple (or now even in native ES) that one could just write them by hand.