[Enhance]: append CSP after meta charset please? #7
Comments
|
Hi :) Just adding a note on breakage: it does happen, with projects with more complexity (e.g: more info to add to the CSP). The Thank you 👍 |
|
Are you using the most recent release? There was a release about 10 days ago that should have solved this. v1.1.1 is the latest |
Hi :) 1.1.1 seems to do the trick, thanks! Out of curiosity: what would it take to inject CSP rules after existing meta tags? Or, at the very least, after the charset one? Cheers! |
## [1.1.2](v1.1.1...v1.1.2) (2022-06-01) ### Bug Fixes * 🐛 html tag location in head ([fc939b2](fc939b2)), closes [#7](#7)
|
🎉 This issue has been resolved in version 1.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
Yeah, the change in where the tags are injected was supposed to be changed in 1.1.1, but I think I must have just forgotten to make the change. The new version 1.1.2 should fix it. |
Hi :)
Thanks for this plugin! Even if it is at an early stage, it looks promising. :)
Prerequisites
Feature Request
Currently, the plugin injects CSP directives at the top of the
<head>. This moves<meta charset="UTF-8" />further down and could potentially break its meaning, scope, and functionality.Since CSP isn't going to suffer from it, I would suggest injecting it right after said meta by default (or even later by using 'head' instead of 'head-prepend')
Cheers and keep up the good work :)
Please and thank you
The text was updated successfully, but these errors were encountered: