packages

I have laid down the ground work for reaching level 6 by typing all class properties and interface methods throughout the codebase, which should already help ensure that types are correct when they get added/copied to getters and such.

I definitely could use help though in reaching level 6, because it's a ton of work left (1465 errors for src/, 400 errors for tests/).

If you are interest

See https://yarnpkg.com/features/pnp#fixing-node_modules

In this install mode (the default starting from Yarn 2.0), Yarn generates a single .pnp.cjs file instead of the usual node_modules folder containing copies of various packages. The .pnp.cjs file contains various maps: one linking package names and versions to their location on the disk and another one linking package names and versions

Github introduced a nice UI for syncing your fork with upstream.

We could use something like that for package links. osc has the setlinkrev command for this.

Some packages may bundle dependencies. We could report outdatedness for these the following way: for outdated packages with single download, propagate outdated status onto the download URL. Then we could show this download specially for other packages, or even make it affect the status.