Skip to content
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

Paths of released source maps refer to relative paths that don't exist #4

Closed
bryanforbes opened this issue Jul 11, 2018 · 0 comments
Closed
Assignees

Comments

@bryanforbes
Copy link
Member

Bug

After building the source, the sources entries in the generated source maps point to source files. For example, after building @dojo/core/lang, the sources entry will be "sources":["../../../src/lang.ts"]. This is fine for development (since the files exist), but once the project is released, the files no longer exist and the dev tools locate the virtual files in strange places. For the release source maps, the sources entry should be corrected to simply be the original filename so that dev tools think the source files are siblings to the JS files.

@bryanforbes bryanforbes self-assigned this Jul 11, 2018
bryanforbes added a commit to bryanforbes/scripts that referenced this issue Jul 11, 2018
bryanforbes added a commit that referenced this issue Jul 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant