@lwrjs/lwc-ssr 0.10.0-alpha.2 → 0.10.0-alpha.3

package/README.md

@@ -102,6 +102,8 @@ There are restrictions on component code for it to successfully render on the se
 
 [LWC synthetic shadow](https://www.npmjs.com/package/@lwc/synthetic-shadow) is not supported during SSR, so components must be able to run using [native shadow](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM).
 
+Root components may not contain [slots](https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.create_components_slots), however slots may still be used in components which are not roots.
+
 ### Loading data during SSR
 
 Many components depend on external data and resources. LWR provides a `getPageData()` hook for developers to fetch data on the server. During SSR, LWR calls the `getPageData()` hook for each **root component**, then serializes the resulting data into the page document as either [JSON](#json) or [markup](#markup).
@@ -246,6 +248,7 @@ Examples of non-portable code and objects include:
 Isomorphic components can:
 
 -   place non-portable code in a function which is not [executed during SSR](#ssr-execution), such as the `renderedCallback`.
+-   choose LWC APIs which are supported on both the client and server (eg: [`lwc:inner-html`](https://rfcs.lwc.dev/rfcs/lwc/0123-innerhtml-binding) over `appendChild()`).
 -   guard non-portable objects so they are not accessed during SSR:
 
 ```js

package/build/es/viewTransformer/index.d.ts

@@ -18,7 +18,7 @@ interface SsrPluginOptions {
  *      f) The SSRed string is used to overwrite/link each custom element (eg: "<c-app></c-app>") in the document (see "stringBuilder.overwrite")
  *      g) A script containing all the serialized properties is added for hydration
  * 4. The view/page document now contains SSRed components, which will be sent to the client
- * 5. During bootstrap on the client, the "lwr/initSsr" module will hydrate ALL the custom elements on the page
+ * 5. During bootstrap on the client, the "lwr/init" module will hydrate ALL the custom elements on the page
  */
 export default function lwcSsrViewTranformer(options: SsrPluginOptions, { moduleBundler, resourceRegistry }: ProviderContext): ViewTransformPlugin;
 export {};

package/build/es/viewTransformer/index.js

@@ -17,7 +17,7 @@ import { ssrElement } from './ssr-element.js';
  *      f) The SSRed string is used to overwrite/link each custom element (eg: "<c-app></c-app>") in the document (see "stringBuilder.overwrite")
  *      g) A script containing all the serialized properties is added for hydration
  * 4. The view/page document now contains SSRed components, which will be sent to the client
- * 5. During bootstrap on the client, the "lwr/initSsr" module will hydrate ALL the custom elements on the page
+ * 5. During bootstrap on the client, the "lwr/init" module will hydrate ALL the custom elements on the page
  */
 export default function lwcSsrViewTranformer(options, { moduleBundler, resourceRegistry }) {
     return {

package/package.json

@@ -4,7 +4,7 @@
     "publishConfig": {
         "access": "public"
     },
-    "version": "0.10.0-alpha.2",
+    "version": "0.10.0-alpha.3",
     "homepage": "https://developer.salesforce.com/docs/platform/lwr/overview",
     "repository": {
         "type": "git",
@@ -34,15 +34,15 @@
     ],
     "dependencies": {
         "@locker/near-membrane-node": "^0.12.0",
-        "@lwrjs/diagnostics": "0.10.0-alpha.2",
-        "@lwrjs/shared-utils": "0.10.0-alpha.2",
+        "@lwrjs/diagnostics": "0.10.0-alpha.3",
+        "@lwrjs/shared-utils": "0.10.0-alpha.3",
         "node-fetch": "^2.6.8"
     },
     "devDependencies": {
-        "@lwrjs/types": "0.10.0-alpha.2"
+        "@lwrjs/types": "0.10.0-alpha.3"
     },
     "engines": {
         "node": ">=16.0.0 <20"
     },
-    "gitHead": "592cda0637513885477829beea35a86407b342d4"
+    "gitHead": "e5c38c00c2ef094961b65e7dffa1ca6ee7c5f734"
 }