https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39151
--- Comment #5 from Paul Derscheid <[email protected]> --- Newer: I found that usage of `yarn check` is discouraged and has better alternatives. Might be worth a try. https://classic.yarnpkg.com/lang/en/docs/cli/check/ I think the below still applies, though: Wrote this first: Can we formalize this a bit more? We need to regularly update npm packages when they become outdated and should then rebuild the lockfile and run CI on it. For the warnings generated in comment #3, this can't really be avoided. A lot of the libraries we use, use outdated dependencies and there's really nothing we can do about that except to hope for upstream dependency updates. We could also fix the warnings about missing peer dependencies by moving the packages which are currently untracked by package.json into node_modules if applicable and silence warnings (but maybe not a good idea) about peer-dependencies that we don't use and therefore don't want. But then we'd need to update a lot of things, not sure whether this is going to resonate well right now :D But I think w/ Vue and so on, we should really put a process for managing js dependencies in place, or rather formalize and improve the process we currently have. --- Just another example, yesterday I looked into the changelog for rspack and noticed that there were some very nice improvements regarding bundle size and bundling speed. I then wondered what the best way to introduce that singular dependency update on bz was. And I nor anyone else should have to wonder about that. No criticism, just an observation :) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
