You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it extracts some dynamic "head code" and saves it in the context.head. So far so good, but it's never used again? Even the /@vite/client and /@react-refresh is manually added again in the meta config. It woudl be in the context.head already, and in a fully dynamic fashion (e.g. if we add more vite plugins).
So is this something that is just "left" from an old refactoring? or has the context.head actually some other meaning? Or can we even re-use it for the to inject the vite's html? (e.g. with dangerouslySetInnerHTML. urgh..?)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm looking into the implementation for getting the right, so far so good, but what I still don't fully understand is the "context.head" property which is also used e.g. here:
https://tanstack.com/router/latest/docs/framework/react/examples/basic-ssr-streaming-file-based
it extracts some dynamic "head code" and saves it in the context.head. So far so good, but it's never used again? Even the /@vite/client and /@react-refresh is manually added again in the meta config. It woudl be in the context.head already, and in a fully dynamic fashion (e.g. if we add more vite plugins).
So is this something that is just "left" from an old refactoring? or has the context.head actually some other meaning? Or can we even re-use it for the to inject the vite's html? (e.g. with dangerouslySetInnerHTML. urgh..?)
Thanks a lot for your ideas and input
Simon
Beta Was this translation helpful? Give feedback.
All reactions