-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[graphiql] generated bundles of graphiql is incompatible with strict CSP #2868
Comments
first of all, we need to replace webpack with vite or use webpack 5 at least, there are two PRs outstanding attempting to do this. but I did not realise that regenerator runtime was re-added, that hasn't been needed for a while since we dropped IE support a few years ago |
Looks like As far as I can tell, there isn't a way to package Update: I tested a locally built version of |
It was in In fact, |
@thomasheyenbrock thanks for the clarification! Lil' tiny PR in (#2939) with the removal. |
Is there an existing issue for this?
Current Behavior
The top level readme in the repo states:
But in fact regenerator-runtime is used here
If I run
build-bundles
in graphiql the generated graphiql.min.js file includes regenerator-runtime and actually differs from the version served here https://graphiql-test.netlify.app/ (the hosted version uses a newer build of regenerator-runtime which doesn't have this issue)The easiest solution would be to remove regenerator-runtime by just removing the one line.
regenerator-runtime was updated recently to fix the issue facebook/regenerator@cc0cde9
If the lib should be kept, we could update regenerator-runtime to 0.14.8 or make sure that strict mode is not used
Expected Behavior
No response
Steps To Reproduce
No response
Module pattern
Environment
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: