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

Redesign: Investigate usage of output.crossOriginLoading of webpack #69

Open
armand1m opened this issue May 22, 2019 · 0 comments
Open

Comments

@armand1m
Copy link
Member

armand1m commented May 22, 2019

Problem

Currently we cannot catch external script errors due to cross-origin policies in the browser. We currently also offer an option through the API in order to disable catching those errors (since we cannot catch them specifically)

Though, it seems that by using output.crossOriginLoading: 'anonymous' in webpack configuration you might be able to actually catch those in a valuable manner. (check https://webpack.js.org/configuration/output/#outputcrossoriginloading)

This issue aims to investigate the possibility of such feature


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

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