Jolyn

I am able to replicate the issue following those steps. Note that pnpm doesn't seem to have the same issue, so perhaps it is yarn-specific.

Wasn't able to replicate the error

I'm open to switching off of nixt if there are some improvements with vitest - do you know of what could be better with it?

I confirmed that this is a bug. It looks like the server rendered content is correct, but that the hydration on the client side is causing the creation of the...

Looked into the code for this and it's because `route.connectedNode` is not being set in the browser since the dom nodes were created server side, so the layout engine thinks...

I've created #150 which fixes this. It's a pretty big change so I need to do further testing before publishing as latest. I've published it as [email protected], under the `beta`...

The bug here isn't very clear - "navigates" could refer to clicking on a link, pressing back/forward, or manually changing the browser url. The settings app could be unmounting due...

No, this isn't yet supported in the layout definition. You can do it in a somewhat roundabout way like this: ```js function applicationDisabled = (appName) => { const disabledApps =...

This isn't currently possible, although I'm not opposed to the feature. One reason I didn't implement this is that it comes with a performance hit - the HTTP headers are...

Also, I'm transferring to single-spa-layout repo, since this is related to that.