-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
[Bug] In-editor breakpoints broken because of source map discrepancies #19401
Comments
This is ultimately a duplicate of these two issues:
We can keep this one open as well (to help ensure folks can find the current investigation and whatnot). The fix will almost certainly be over in ember-cli-htmlbars (doing something smarter with the string concatenation in the colocation build step). |
@rwjblue Checking to see if there's any progress with this issue. I understand there was an attempted fix that didn't go through. Is there any other attempt planned to fix it the right way? |
We are also running into this issue and hoping for a workaround. |
In terms of tooling and DX, this would make a huge difference in our team. I am quite surprised that this issue does not attract more attention in the community 😞 |
Just spent so long trying to get debuggers to work and it was once again another ember issue that is years old. |
@robclancy This issue is indeed old, but there is a path forward with First Class Template components and |
🐞 Describe the Bug
The in-IDE debug/breakpoint experience for developers working on Ember apps is currently broken because of the difference in rendered source maps vs the source code in the code editor.
Example: For a component with a colocated template, like so:
The generated source map looks like so:
These extra two lines at the top of the source map pushes all lines in the component down, resulting in discrepancy in breakpoint line numbers. Breakpoints in browser's developer tools still work fine. But for breakpoints set in JS files in code editors (Example: VS Code) where the two lines don't exist, the line numbers don't match and the debugging experience is broken as a result
🔬 Minimal Reproduction
😕 Actual Behavior
Viewing code with sourcemap applied shows two extra lines of code at the top of the component
🤔 Expected Behavior
Source maps should map exactly to the source the developer is working on
🌍 Environment
➕ Additional Context
I have consistently verified this behavior for components, but I haven't looked at such possible discrepancies in other types of JS files like services and routes. I'll update this bug if I find more other occurrences of this issue beyond components.
The text was updated successfully, but these errors were encountered: