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.

Sign up for GitHub

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

Jump to bottom

Content Security Policy unsafe-eval and unsafe-inline still required? #2480

Open
2 of 10 tasks
joehuang-seismic opened this issue Jan 17, 2024 · 1 comment
Open
2 of 10 tasks

Content Security Policy unsafe-eval and unsafe-inline still required? #2480

joehuang-seismic opened this issue Jan 17, 2024 · 1 comment

Comments

@joehuang-seismic
Copy link

joehuang-seismic commented Jan 17, 2024 •
edited

  • SystemJS Version: 6.10.2
  • Which library are you using?
    • system.js
    • s.js
    • system-node.cjs
  • Which extras are you using?
    • AMD extra
    • Named Exports
    • Named Register
    • Transform
    • Use Default
    • Global
    • Dynamic Import Maps
  • Are you using any custom hooks? Yes
    • compiler.hooks.compilation.tap
      • compilation.hooks.afterOptimizeChunks.tap

Question

I saw from this old comment #2172 (comment) that SystemJS depends on unsafe-eval and unsafe-inline CSP to work, is this still the case? If so, are there any suggestions to accommodate the removal of those CSP rules? From what I've found, it looks like eval is still in use, and we still need to apply those unsafe CSP rules. Any insights would be greatly appreciated, thanks!
@guybedford
Copy link
Member

SystemJS is very much CSP compatible, it's only when using the transform or fetch extras that this is not the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@guybedford @joehuang-seismic