Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
scripts
See original GitHub issueI’m currently using Helmet but I do prefer the hooks approach you offer.
One thing I’m missing is <script> support. It’s nice to be able to encapsulate trackers and other scripts that have to go in <head> for technical reasons so they can be placed where they make sense in the application.
Helmet’s support for <script> is very rudimentary IMHO - it just adds the tag without regards for SSR-rendered previous tags, and if you put in an inline script, it won’t run it, so that will only work for SSR.
So, ideally, hoofd would:
- support script tags
- mark SSR-ed script tags in a way they can be recognized after hydration
- only add script tags once, also after hydration
evalinline scripts when run in the browser, but add them to<head>when run during SSR
But, I would already be happy with simply supporting the tag.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ah damn, forgot about that 😅
Closing and pushing #35 and #31 in a 1.2.0 release