-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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: ensure that each js file served up by vite dev server has an inline sourcemap #30606
fix: ensure that each js file served up by vite dev server has an inline sourcemap #30606
Conversation
…-in-vite-dev-server-has-a-sourcemap
cypress Run #58405
Run Properties:
|
Project |
cypress
|
Branch Review |
ryanm/fix/ensure-that-each-served-js-file-in-vite-dev-server-has-a-sourcemap
|
Run status |
Passed #58405
|
Run duration | 17m 41s |
Commit |
46206bf448: Merge branch 'develop' into ryanm/fix/ensure-that-each-served-js-file-in-vite-de...
|
Committer | Ryan Manuel |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
2
|
Pending |
77
|
Skipped |
0
|
Passing |
5588
|
View all changes introduced in this branch ↗︎ |
Warning
No Report: Something went wrong and we could not generate a report for the Application Quality products.
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.
does this fix the code frame issue we were seeing with vite and component testing?
Unfortunately, no that is more complicated to resolve however this will get us where we need to get to in order to properly have sourcemaps available in the protocol space. |
…-in-vite-dev-server-has-a-sourcemap
…-in-vite-dev-server-has-a-sourcemap
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Additional details
We have a custom vite dev server plugin that transforms JS files to include inlined source maps but there were two scenarios that were missed with this plugin:
This PR resolves both of these scenarios.
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?