E902
Error
Syntax and structure
E902 — Output its own security policy refuses
The build holds every page to the content security policy it ships beside it — as it wrote the page, and as the page's own head { } tags would add to it; something there would be blocked.
The fix
what the
message says; a library's origin goes in meta.scripts, a stylesheet's in
meta.stylesheets.
Why this rule exists
The build holds every page it writes to the content security policy it
ships beside it; something on this page — an inline script, a style=, a
script from an origin the policy never named — would be blocked. A page's
own head { script(src: …) } or head { link(rel: "stylesheet", href: …) }
is held to it too, where it is written: the tag is added on the live page,
and the browser would refuse it there without a word.
lints cannot lower it: it would ship a broken page.