Lock all dependencies in NPM

[joaomoreno]

A few dependencies are currently loosely locked as commits or branches in git repositories:

• chokidar@bpasero/chokidar#vscode - @bpasero
• v8-profiler@jrieken/v8-profiler#vscode - @jrieken
• xterm@Tyriar/xterm.js#vscode-release/1.19 - @Tyriar

In order to improve dev performance, we shouldn't use this syntax any more. There are two options:

• Integrate the changes into the upstream project and depend on that
• Start publishing that fork into NPM under a different name

[bpasero]

@joaomoreno my latest experiments with chokidar is that we might no longer need my custom fork. It looks like I can npm install latest and it will fallback to compiling fsevents if node-pre-gyp fails. That is quite awesome! So maybe we do that as part of the yarn update 👍

[joaomoreno]

It would be great to do it in master first, I'll merge that over to yarn.

[bpasero]

@joaomoreno we bike?

[jrieken]

I wanna explore not having the v8-profiler dependency anymore...

[joaomoreno]

@jrieken Please do!

[bpasero]

I published vscode-chokidar@1.6.1

[joaomoreno]

@Tyriar Don't forget to also update https://github.com/Microsoft/vscode/wiki/Working-with-xterm.js accordingly once you do this.

[joaomoreno]

FYI For chokidar, @bpasero went with the option of creating a vscode-chokidar module, simply because chokidar depends on node-pre-gyp as a regular dependency... which would end up in our release, unnecessarily.

[jrieken]

v8-profiler is gone, say hallo to to v8-inspect-profiler (which is on npm)

[Tyriar]

We now use vscode-xterm from npm, instructions updated at https://github.com/Microsoft/vscode/wiki/Working-with-xterm.js

[joaomoreno]

@Tyriar Excellent, thanks!