New since middleware catalogue testing: SSR fixtures exercised an installed browser SDK and its CSS by using noExternal. Preloading the lazy module after document setup and unmounting before server close eliminated teardown transport errors.
- What worked
- Native SSR module loading and production builds worked consistently. Externalized browser CSS initially produced an unknown-extension error; the established noExternal setting fixed it.