It looks like they turned some eslint warnings on. Or we had them off and I
turned them on. They also added a new target which had the name monaco in it.

Looks like they modified a few of the cases related to Reconnection.

As Asher pointed out, looks like it makes #2381 obsolete.

Hope this all works.

It looks like they added a few more variables and cleaned this file up.

I removed the yarn and yarnRc stuff. Hope that doesn't break anything.

Looks like they modified the function signature for _loadCommonJSModule.

I believe the first param is now the extensionId or null. Probably for logging
reason guessing.

Looks like they added two lines in the open method.
1. Logging for workbench configuration
2. Window - creating a BrowserWindow

Again, hope this was correct.

It looks like they moved around a few lines here.

If there are issues with dependencies not installing, check here.

I hope this was done correctly.

It upgraded a few packages, we left out the electron packages and it added two
resolutions.

From what I can tell, they added these `performance.mark` calls. Not sure
exactly what they do, but my guess is they're supposed to help with measuring
extension performance?

These seem to be used in some "getting started" page but I'm not sure
where it is.

We used this to run vscodevim in the browser but it now has a version
that is able to run as a VS Code web extension. This does require an
update to our marketplace, however.

Now that you can customize the home it's probably fine to show it.
There's also an option for users to hide it.

It's probably registered in some other way now.

A new doStore was added.

We've always had this.

Since we're following the VS Code allowed version range now to prevent
bugs use the new range instead of commenting it out.

Modify the tsconfig.json in lib/vscode/src/build.

This adds the flag skipLibCheck: true to tell TypeScript
to not type-check the declaration files at build time.

We need to add this because otherwise it checks the declaration
files and reports an error of duplicate type definitions
because we use Jest for our tests and they use Mocha and they
both use the global namespace "test" in their .d.ts files.

Add a short message above the search box on the Extensions panel. This
helps explain the extension divergence to the user.

If they click dismiss, it stores an item in localStorage to prevent the
message from showing up on subsequent loads.
Co-authored-by: NAsher <ash@coder.com>