| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Are any of these updates needed? In general I avoid updating dependencies unless there's a reason to do so. If things work no reason to get exposed to API changes, regressions, new bugs |
Sorry, something went wrong.
|
Not currently needed per se, just maintenance, so we don't need to check the changelog of 30 versions of those dependencies in 5 years when we really need to upgrade because of a blocker like we had with budo and self-signed certificate not working on ubuntu 22.04. Please be aware that we don't push package-lock.json in the repo, so we effectively auto upgrade all those dependencies when you freshly git clone the repo and run npm install.
that removes support for node 16.x. That's the only api changes as far as I'm aware after reading the changelogs. The dist didn't change after those upgrades. Feel free to leave it open until we really need it. I'll just update it the next time I read the changelogs in a year :D |
Sorry, something went wrong.
|
@dmarcos now that the bot is using node 22.7.0 I don't see any reason to not merge this. |
Sorry, something went wrong.
|
@vincentfretin is this a one time thing or we will have to continuously update webpack and stuff. Would prefer to avoid get on the train of updating packages just for the shake of it. Can of course update if there's a reason to do so |
Sorry, something went wrong.
|
That's a one time thing to remove a dependency, otherwise I wouldn't have bothered to do this PR. |
Sorry, something went wrong.
…m version required, remove webpack-merge, webpack now supports extending another configuration
|
Thanks! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description:
Update build tools dependencies.
Changes proposed: