asyncapi / asyncapi/asyncapi-react

Angular integration fails due to CSP violation

Open
#1,187 4 comments 3 reactions 0 assignees View on GitHub
stale
Dominant language
TypeScript
Stars
243
Forks
182
Avg merge
3d 6h
Merged PRs (30d)
11

Description

**Description**

We attempted to implement the AsyncAPI React component in an Angular project following the documentation:
“Using in other technologies” → “Using in Angular”
https://github.com/asyncapi/asyncapi-react/blob/master/docs/usage/angular.md

When running the implementation, we encounter the following error

Image

**Current Workaround**

The component only works if we relax the Content Security Policy (CSP) by adding 'unsafe-eval' to the script-src directive.

**Questions / Request for Guidance**

- Is there a plan to address this issue so that 'unsafe-eval' can be avoided?
- Is there a recommended workaround that does not require relaxing the CSP?

Contributor guide

Open the contributing guide

Research direction

Start with docs/usage/angular.md and reproduce the documented Angular integration, then inspect the reported CSP violation and the component bundle or entry point involved. Done means the AsyncAPI React component works in Angular without requiring 'unsafe-eval', or the documentation clearly records a supported workaround if that is not possible.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, react, typescript
Domain
frontend, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.