Fix loading mappings.wasm on authenticated URLs

[chrisbreiding]

• Closes Request cannot be constructed from a URL that includes credentials: /__cypress/runner/./wasm/mappings.wasm #7481

User facing changelog

• Fixed an issue where authenticated URLs would error with Request cannot be constructed from a URL that includes credentials: /__cypress/runner/./wasm/mappings.wasm

Additional details

For the sake of source maps and all their goodness, we use the source-map package. It needs to load a mappings.wasm file in order to parse the source map. Previously, we provided a url to the mappings.wasm file and the source-map package loaded it asynchronously via fetch.

This worked fine in most cases but failed when the URL was authenticated, because the fetch needs to be authenticated too.

The fix is that, instead of having the mappings.wasm loaded asynchronously, we provide it to the source-map package synchronously as an ArrayBuffer. Therefore, no fetch and no issues with loading it regardless of the URL.

How has the user experience changed?

Any spec run on an authenticated URL would error and fail immediately. Now those specs run normally.

PR Tasks

• Have tests been added/updated?
• Has the original issue been tagged with a release in ZenHub?
• N/A Has a PR for user-facing changes been opened in cypress-documentation?
• N/A Have API changes been updated in the type definitions?
• N/A Have new configuration options been added to the cypress.schema.json?

[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

7445 • 0 • 104 • 0

---

Run details

Project	cypress
Status	Passed
Commit	e44f127
Started	Jun 1, 2020 7:34 PM
Ended	Jun 1, 2020 7:42 PM
Duration	07:55 💡
OS	Linux Debian - 10.1
Browser	Multiple

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

[jennifer-shehane]

Manually verified this fixes the issue. Test also covers use case. 👍