-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Use production build config for cypress tests and fix webpack #16978
Conversation
Codecov Report
@@ Coverage Diff @@
## master #16978 +/- ##
==========================================
- Coverage 76.93% 76.93% -0.01%
==========================================
Files 1030 1030
Lines 55019 55019
Branches 7465 7465
==========================================
- Hits 42331 42330 -1
- Misses 12434 12435 +1
Partials 254 254
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* fix: Use production build config for cypress tests * set usedExports to global
🏷 v1.4 |
* fix: Use production build config for cypress tests * set usedExports to global (cherry picked from commit 2757b93)
* fix: Use production build config for cypress tests * set usedExports to global
SUMMARY
Recently we had an issue that only reproed with production build assets. I suspect this would've been caught with cypress, but we build assets in development mode for cypress, so it wasn't caught. This PR should run cypress on prod assets instead of dev ones.
This pr also further resolves the webpack bugs by setting usedExports to globa.
TESTING INSTRUCTIONS
CI
ADDITIONAL INFORMATION
to: @eschutho @michael-s-molina @rusackas