Enhancement/issue 1088 refactor Workers out of SSR builds

[thescientist13]

Related Issue

resolves #1088

Summary of Changes

1. Refactor Workers out of serving SSR pages
2. Pre-compile static HTML templates as local variables at build time
3. Refactor renderer plugin to just be a function (not tied to Workers implementation)

References

• Serverless SSR pages greenwood-demo-adapter-vercel#1
• Serverless SSR pages greenwood-demo-adapter-netlify#3

TODO

1. confirm static templating works, e.g. src/templates/
2. Will still need the concept of an executeModule for custom implementations like Lit (do we have to handle a renderer and an adapter plugin at the same time?) and for development
3. get executeRouteModule from config
4. simplify executeModule signature (pass in entire page)
5. Update static router serve spec per new implementation
6. refactor lit renderer and get all specs passing
7. Is it OK to reference executeModuleUrl in our wrapper bundles? Can we bundle down into one file instead?
8. Likely we don't need to output templates/ dir anymore?
9. What about os / thread pooling for prerendering? - deferred to performance benchmarking / optimizing Greenwood #970 and Encapsulating SSR Rendering (Isolation Mode) #1117
10. Docs
    • prerender plugin
    • getTemplate is a "static" function - deprecating anyways?
    • make a discussion for how best encapsulate SSR?
11. Test in adapter demo repos
12. Test in Benchmarking repo - deferred to performance benchmarking / optimizing Greenwood #970
13. Clean up TODOs / console logs

Questions

1. getTemplate has to be a "static" function (for now) but maybe we will deprecating anyways as part of Layouts (Templates) and Pages #955 ? - deferred to Static and Serverless Hosting Runtime Adapters #1008
2. Create a discussion to evaluate alternatives to Workers, or making it opt-in? Or maybe I'm just over thinking it? Would be good to cross reference as part of Static and Serverless Hosting Runtime Adapters #1008 - Encapsulating SSR Rendering (Isolation Mode) #1117
3. Can we ever "bundle down" to a single file executable for SSR pages? - single file bundles (SFBs) for SSR page and API routes #1118
4. How to handle something like Netlify which needs custom handling for import.meta.url? - deferred to - Static and Serverless Hosting Runtime Adapters #1008 (comment)

   await fs.writeFile(outputUrl, `
     import 'wc-compiler/src/dom-shim.js';
     import Page from './_${filename}';
   
     export async function handler(request) {
       console.log('${JSON.stringify(page)}');          
   
       let initBody = ${body};
       let initHtml = \`${html}\`;
   
       if (!initBody) {
         const page = new Page();
         await page.connectedCallback();
   
         initHtml = initHtml.replace(\/\<content-outlet>(.*)<\\/content-outlet>\/s, page.innerHTML);
       }
   
       return new Response(initHtml);
     }
   `);