Launch(?) tasks

[wanderingstan]

• Identify good exemplar / demo-able error situations where this could shine.
  • Plain error
  • Using stack trace??
  • Occurs in github issue
  • Spike in last hours?
• Search logged errors for matches with other users (self). Some stats
  • Create query page for our server
• Filter out variables (presumably by keeping list of all words in JS errors, or even all words from SO answers)
• Some way to set (or detect??) the repo/github page
  • Get dependences (package.json) from repo
  • Get org members from repo (?) to give team reports
• Expand searches to include dependencies
• Some logic to detect a "strong match", i.e. an SO question-answer pair that is super upvoted and very closely matches our search terms (bonus points if search includes dependencies, odd variable names, or our stack trace)
• Migrate our server to real cloud solution. Google cloud? Azure?
• Extract EC logic into library that can be included on page, no extension needed (for demo!)
• Convert this ext to use npm, or create new extension (with npm) and copy over error-catching logic
• Move this repo into ec main repo?
• Some stats/analytics page on server to show off data