feature/discussion 1117 Isolation Mode (v1)

[thescientist13]

Related Issue

#1117 (somewhat restores - #1110)

Introduces Worker threads as part of the greenwood serve lifecycle when expressed through the a file level export enabling it, which will ensure the page does not get executed in the global scope of the NodeJS process.

// src/pages/products.js
export const isolation = true;

This aims to help address various issues observed with trying to support DOM shims on the server

• customElements.define already called for Lit SSR integration - demo/restore products page and upgrade to Lit v3 thescientist13/greenwood-lit-ssr#9
• duplicate loading of WCC DOM shim causes infinite SSR page loading loop - duplicate loads of the DOM shim leads to an infinite rendering issue wcc#147
• general alignment with web standards - CustomElementsRegistry Spec Implementation alignment wcc#145

Summary of Changes

1. Add opt-in / out isolation mode for SSR pages and add test case
2. Add opt-in / out isolation mode for API routes and add test case
3. Default Settings
   • WCC - false
   • Lit - true
4. Added global configuration for isolation mode
5. Add documentation and test cases

TODO

1. Add global configuration option
2. Docs
   • configuration docs
   • SSR route docs
   • API docs
   • Data sources / graph docs? - N / A
   • adapters / execute route module for export const isolation = true - N / A
3. Finalize default settings for plugins and docs
   • WCC - false
   • Lit - true
4. Clean up console logs / comments
5. refactoring (nice to have)
   • ssr-route-worker filenames are a little clunky
   • Should we re-use thread pool? - maybe?
     • actually no, we should let user's decide on how to scale their own servers, we shouldn't cap anything in production
   • get more options from the graph / module instead upfront instead of in execute route module - will save for eliminate SSR page instantiation during graph lifecycle #991

Question

1. Should it be set to true by default?
   • Lit one one probably should be at least, and should be documented
   • Default can be no (for now - CustomElementsRegistry Spec Implementation alignment wcc#145)