Set CommonJS module format when transpiling TS code

[bahmutov]

• Closes Typescript support: Update documentation for plugins.ts #7005
• Closes typescript compilerOptions "module" param breaks cypress #7151
• Closes Typescript support: Electron is reading the wrong tsconfig.json #7043
• Closes plugins.js - async/await causes invalid import errors #7011

User facing changelog

Default TypeScript options now set module: commonJS which Node and the browser expect. Before this PR user could set module: nextjs in their tsconfig.json and nothing would work if you had import or async keywords in the source code.

How has the user experience changed?

Previously failing projects should work.

PR Tasks

• Have tests been added/updated?
• Has the original issue been tagged with a release in ZenHub?

[cypress-bot]

Thanks for the contribution! Below are some guidelines Cypress uses when doing PR reviews.

• Please write [WIP] in the title of your Pull Request if your PR is not ready for review - someone will review your PR as soon as the [WIP] is removed.
• Please familiarize yourself with the PR Review Checklist and feel free to make updates on your PR based on these guidelines.

PR Review Checklist

If any of the following requirements can't be met, leave a comment in the review selecting 'Request changes', otherwise 'Approve'.

User Experience

• The feature/bugfix is self-documenting from within the product.
• The change provides the end user with a way to fix their problem (no dead ends).

Functionality

• The code works and performs its intended function with the correct logic.
• Performance has been factored in (for example, the code cleans up after itself to not cause memory leaks).
• The code guards against edge cases and invalid input and has tests to cover it.

Maintainability

• The code is readable (too many nested 'if's are a bad sign).
• Names used for variables, methods, etc, clearly describe their function.
• The code is easy to understood and there are relevant comments explaining.
• New algorithms are documented in the code with link(s) to external docs (flowcharts, w3c, chrome, firefox).
• There are comments containing link(s) to the addressed issue (in tests and code).

Quality

• The change does not reimplement code.
• There's not a module from the ecosystem that should be used instead.
• There is no redundant or duplicate code.
• There are no irrelevant comments left in the code.
• Tests are testing the code’s intended functionality in the best way possible.

Internal

• The original issue has been tagged with a release in ZenHub.

[cypress]

---

Test summary

3351 • 0 • 49 • 0

---

Run details

Project	cypress
Status	Passed
Commit	17a1e55
Started	May 3, 2020 7:01 PM
Ended	May 3, 2020 7:07 PM
Duration	05:21 💡
OS	Linux Debian - 10.1
Browser	Firefox 74

View run in Cypress Dashboard ➡️

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[tgriesser]

I think we may want to allow for more options for folks to specify which tsconfig file they want to use explicitly, and/or whether transpileOnly is true. But for now I'm 👍 on this change.

[sainthkh]

LGTM. I found only a minor error. 👍

[brian-mann]

@tgriesser can you rereview and approve? i accepted one change from @sainthkh that caused your review to be dismissed