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

A question about chunk sourcemaps #4741

Closed
andershagebakken opened this issue Feb 16, 2017 · 2 comments · Fixed by #4742
Closed

A question about chunk sourcemaps #4741

andershagebakken opened this issue Feb 16, 2017 · 2 comments · Fixed by #4742

Comments

@andershagebakken
Copy link

Hi. I was just wondering why the sourcemap file is named as follows: 0.93f2....bundle.map. but the js chunks are named as such: 0.93f2....chunk.js ? The reason I am wondering is that I am using sentry.io, and I upload the sourcemaps I get when building with --prod --aot --sourcemap to sentry.io, instead of making them public. Sentry.io can not detect the sourcemap reference because the names does not match, as they do with main, styles, inline and vendor. Thanks in advance, and the great work you do with this tool.

@angular/cli: 1.0.0-beta.31
node: 6.9.5
os: darwin x64

@filipesilva
Copy link
Contributor

That's a bug actually, good catch!

filipesilva added a commit that referenced this issue Feb 16, 2017
Fix #4741

BREAKING CHANGE: sourcemaps now are always [filename].map (e.g `main.bundle.js.map` instead of `main.bundle.map`).
hansl pushed a commit that referenced this issue Feb 17, 2017
Fix #4741

BREAKING CHANGE: sourcemaps now are always [filename].map (e.g `main.bundle.js.map` instead of `main.bundle.map`).
asnowwolf pushed a commit to asnowwolf/angular-cli that referenced this issue Apr 12, 2017
Fix angular#4741

BREAKING CHANGE: sourcemaps now are always [filename].map (e.g `main.bundle.js.map` instead of `main.bundle.map`).
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants