Deploying changes to SolidStart app then navigating the application throws strange error
Before I file this as an official issue or start nagging the rest of the team I want to make sure I'm not deploying or thinking about the issue incorrectly. Basically I'm deploying a SolidStart app on Cloudflare Workers, loading it on my browser, pushing a deploy and noticing that when I navigate between pages an error is thrown.
I could be wrong but it seems to happen mostly with Outlets. When I navigate to a page with one, the application loads the nested chunked script that was compiled newly while the one currently cached in browser is older. Hence the child trips up and throws an error because the function it depends on no longer exists. So I see a lot of red errors as a result.
How should I be deploying this to ensure that the function names between versions remain consistent and my deployments don't break? or is this a bug with Start's default config....
CSS Transition does not get animated properly when applied in style={} directly
I have a navbar which I have animated (attached), however to achieve this effect I needed to go in a roundabout way.
Basically, the transition needs to switch directions based on which path the user is navigating to, and the issue is that if I compute the transition in the
style prop of the div, then the transition updates only after the transition has occurred, rather than influencing the transition. To solve this, I have an effect that sets the style programmatically before the signals are flushed, causing the transition to animate properly.
```tsx
createEffect<number>((prevIndex) => {...
Route layout not define
What does this mean and how can i fix it. I am using storybook and i realize if there is an A tag in the component i get this error in my storybook.
How do you refer to a deeply nested component?
Take the two tweet buttons in the screenshot for example, I would like to focus on the tweet textarea when the user clicks on the big tweet button. How can this be done? Thanks!
