Make vscode-jest Official

[orta]

Make vscode-jest Official, and allow it to share the majority of the code with a potential nuclide version.

TODO

• Decide on repo? (would this be a npm module as a lerna thing? @cpojer)
• TypeScript -> Flow
• Convert from mocha -> Jest
• Start to decouple VS Code from the codebase. This means only Extension.ts is allowed to use import {workspace} from 'vscode'; as a bare minimum.
• Try to remove hacks/string parsing that could be fixed by officially supporting things inside Jest
  • Getting Jest Version
  • Getting Jest Config
  • actually that entire config reader is a tad hacky, make that all structured JSON data
  • add a "terse" message for any fail

[cpojer]

Awesome.

Let's put all of these into packages/ inside of Jest. If you can reserve the package names on npm and add me (cpojer) and the "fb" user to it, that will be great. We can then start publishing from within this repo. We may need to figure out some permissions but that shouldn't be that big of a deal :)

[orta]

So deployment of vscode packages isn't done via npm, ( that's a whole thing) so we don't need to claim it for vscode-jest, and from the look of it, we don't need to from atom (from a quick look at a tutorial.)

So, unless you think it makes more sense to have a jest-editor-support package that they both rely on, which I'm amiable to, then we don't need to claim anything?

[cpojer]

Oh that's interesting, I was unaware. I definitely think we should split everything up into a jest-editor-support package (or many) and then find a way to publish the vscode package. For atom, we should do exactly the same: push most of the code into the editor support package and the atom specific code into a separate package that we deploy via apm. Does that make sense?

[orta]

Yep 👍

[orta]

This is done 👍

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.