E0550 Content-Security-Policy setting that cannot be used
Words in italics are filled in when the compiler reports it, such as the element's name or the list of known ones.
Why
A web build writes a strict Content-Security-Policy into every copy of the app shell and into _headers (decision 0150). security.content-security-policy in duolith.yaml changes it: a group of directives adds sources to the default (connect-src: [https://api.example.com]), a policy written out as one line replaces it, with the shell's own script hashes, 'self' and the inline styles it needs merged in, and off writes none. The build stops on anything the browser would read differently from what was meant: a duolith.yaml that is not YAML, a key under security that is not a setting (content-security-policy is the one), a directive no browser knows (conect-src), a directive written twice, a source that is not text (8080) or holds a space, ; or ,, a keyword without its single quotes (self, which a browser reads as a host name), a quoted word that is not a keyword, 'unsafe-inline' for scripts, which browsers ignore next to the shell's hashes, and a hash or nonce for styles, which would make them ignore the 'unsafe-inline' the shell's styles need. A directive that takes no sources, such as upgrade-insecure-requests, is written with true.
How to fix it
List each source as its own item under its directive, with keywords in single quotes inside the YAML quotes, such as script-src: ["'self'", https://cdn.example.com] or connect-src: [https://api.example.com, wss://live.example.com]. To replace the whole policy, write it on one line in quotes; to write none, use off.
In a terminal
duolith explain E0550