-
Notifications
You must be signed in to change notification settings - Fork 128
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
@shopify/shopify-api source maps don't point to source files #1208
Comments
We're labeling this issue as stale because there hasn't been any activity on it for 60 days. While the issue will stay open and we hope to resolve it, this helps us prioritize community requests. You can add a comment to remove the label if it's still relevant, and we can re-evaluate it. |
I can confirm the issue still occurs and is still valid. Do we have an update on this or were you able to resolve this? |
We're labeling this issue as stale because there hasn't been any activity on it for 60 days. While the issue will stay open and we hope to resolve it, this helps us prioritize community requests. You can add a comment to remove the label if it's still relevant, and we can re-evaluate it. |
Still relevant for me, I see this whenever i run my Hydrogen app in dev mode:
|
Also experiencing the same warnings with Hydrogen App. Were you able to fix this? |
Nope, not yet |
Issue summary
Before opening this issue, I have:
@shopify/*
package and version:{ logger: { level: LogSeverity.Debug } }
in my configuration, when applicableESM source maps don't point to the source file because they go up 7 directories instead of the correct 5, for example:
../../../../../../../rest/admin/2024-04/index.ts
instead of the correct../../../../../rest/admin/2024-04/index.ts
Expected behavior
Source maps point to the source file.
Actual behavior
Source maps don't point to the source file because
Steps to reproduce the problem
Debug logs
When building and aliasing to the local project, and running
shopify app dev
using the aliased local project:The text was updated successfully, but these errors were encountered: