misc

[Rich-Harris]

fixes a couple of issues encountered in an app using kit@next:

• the Vite SSR module graph doesn't distinguish between statically and dynamically imported modules, which (I think) somehow causes virtual CSS files to be requested when Kit tries to collect critical CSS for the page even though it's not available yet. I don't totally understand the mechanics of it, but bailing when Vite can't load the module in question fixes it
• we don't have control over when the SSR module cache is invalidated in dev mode. This means that the effects of set_paths don't persist, which means that anything importing base or assets from $app/paths will get undefined values. Since custom base and assets values only make sense in a deployed app anyway, we can fix that by not calling set_paths in dev mode and instead initialising them with the expected values. Still need to find a solution to Some way to get advance warning of incorrect asset paths #326

[benmccann]

should we print a warning or something in the meantime so that if a user hits this they won't be totally stumped as to why?

[Rich-Harris]

No, we don't want the user to be aware that this is happening