Master work tracking issue

[roblourens]

Our first priority is to be able to publish this extension in a form where anyone can install it and use it with their existing node/chrome configs in the same way they are used to, and also try out the new features. In order to publish it to the vscode marketplace, we don't need 100% of the existing features implemented, but it needs to be basically usable, have basic telemetry, and logging for users who report issues.

• Implement basic node/chrome launch configs
• Implement all launch config flags
  • Launch Config Parity #26
  • We can start putting it in front of people with many of these boxes unchecked - not sure where we will draw the line exactly
• Implement telemetry
  • Started in Added basic telemetry #54
  • Include GDPR annotations and publish
• Implement logging
  • Implement logging #55
• Stabilize/fill out tests
  • The existing tests are very unstable: Improve test reliability + make them runnable on PR builds #28
  • The imported Chrome integration tests are mostly failing: Integration test status #44
  • Need to consider bringing over integration tests from node2 as well
• Decide what to call it and how to communicate the change to users

---

• CELA Product scan?
• Security review?

---

Test gaps reported by the VS team, will want to eventually fill these as well: https://devdiv.visualstudio.com/DevDiv/_wiki/wikis/DevDiv.wiki/2049/JavaScript-debug-adapters-V2?anchor=preliminary-list-of-things-to-test-on-an-integration-level

Feature gaps: https://devdiv.visualstudio.com/DevDiv/_wiki/wikis/DevDiv.wiki/3608/Comparing-V1-2-to-PWA

[connor4312]

This has been mostly completed or in progress in other issues, let's use individual issues and milestones for ongoing work.