This updates dependencies on the main project and all sub-projects. After these updates, npn reports no vulnerabilities (for now) on all of them, with the exception of metapi, which has code that depends on an old version of jsdom. For metapi, there are 5 moderate severity vulnerabilities remaining. Updating to remove those will require code changes to metapi.
This updates both xo and eslint to their current versions: xo@0.46.4 and eslint@8.3.0, which have substantial improvements and support for new JavaScript syntax. The new syntax support should allow the use of some things which are, at this point, already well supported by browsers. There are several new code quality rules. All of those have been addjusted in in all projects such that they don't require changes from any projects other than AIM and FIRE, which I was working on anyway and planned to have compatible.
While there are no code changes that are forced by these updates, there are changes which would be beneficial when the code in each project is next updated. If you're working on one of the projects, then it would be helpful to look at what settings have been disabled, or where there are overrides applied as a way to see what might be improved.
This updates dependencies on the main project and all sub-projects. After these updates,
npnreports no vulnerabilities (for now) on all of them, with the exception of metapi, which has code that depends on an old version ofjsdom. For metapi, there are 5 moderate severity vulnerabilities remaining. Updating to remove those will require code changes to metapi.This updates both
xoandeslintto their current versions: xo@0.46.4 and eslint@8.3.0, which have substantial improvements and support for new JavaScript syntax. The new syntax support should allow the use of some things which are, at this point, already well supported by browsers. There are several new code quality rules. All of those have been addjusted in in all projects such that they don't require changes from any projects other than AIM and FIRE, which I was working on anyway and planned to have compatible.While there are no code changes that are forced by these updates, there are changes which would be beneficial when the code in each project is next updated. If you're working on one of the projects, then it would be helpful to look at what settings have been disabled, or where there are overrides applied as a way to see what might be improved.