npm - create-sitecore-jss - Versions diffs - 20.0.0-canary.78 - Mend

create-sitecore-jss 20.0.0-canary.78

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (166) hide show

package/dist/templates/nextjs/src/pages/_error.tsx ADDED Viewed

@@ -0,0 +1,35 @@
+import { NextPage } from 'next';
+import Head from 'next/head';
+interface ErrorPageProps {
+  statusCode?: number | null | undefined;
+}
+/**
+ * Rendered for 500 errors on both server and client. Used only in Production mode.
+ * @link https://nextjs.org/docs/advanced-features/custom-error-page#more-advanced-error-page-customizing
+ */
+const ErrorPage: NextPage<ErrorPageProps> = ({ statusCode }) => (
+  <>
+    <Head>
+      <title>Error</title>
+    </Head>
+    <div style={{ padding: 10 }}>
+      <h1>An error occurred</h1>
+      <p>
+        {statusCode
+          ? `A server-side ${statusCode} error occurred.`
+          : 'A client-side error occurred.'}
+      </p>
+      <a href="/">Go to the Home page</a>
+    </div>
+  </>
+);
+ErrorPage.getInitialProps = ({ res, err }) => {
+  const statusCode = res ? res.statusCode : err ? err.statusCode : 404;
+  return { statusCode };
+};
+export default ErrorPage;

package/dist/templates/nextjs/src/pages/api/editing/data/[key].ts ADDED Viewed

@@ -0,0 +1,24 @@
+import { EditingDataMiddleware } from '@sitecore-jss/sitecore-jss-nextjs/middleware';
+/**
+ * This Next.js API route is used to handle Sitecore Experience Editor data storage and retrieval by key
+ * (between the Sitecore Experience Editor POST and Next.js page render requests) via the `EditingDataService`.
+ *
+ * The `EditingDataMiddleware` expects this dynamic route name to be '[key]' by default, but can
+ * be configured to use something else with the `dynamicRouteKey` option.
+ */
+// Bump body size limit (1mb by default) for Experience Editor payload
+// See https://nextjs.org/docs/api-routes/api-middlewares#custom-config
+export const config = {
+  api: {
+    bodyParser: {
+      sizeLimit: '2mb',
+    },
+  },
+};
+// Wire up the EditingDataMiddleware handler
+const handler = new EditingDataMiddleware().getHandler();
+export default handler;

package/dist/templates/nextjs/src/pages/api/editing/render.ts ADDED Viewed

@@ -0,0 +1,30 @@
+import { EditingRenderMiddleware } from '@sitecore-jss/sitecore-jss-nextjs/middleware';
+/**
+ * This Next.js API route is used to handle POST requests from the Sitecore Experience Editor.
+ * This route should match the `serverSideRenderingEngineEndpointUrl` in your Sitecore configuration,
+ * which is set to "http://localhost:3000/api/editing/render" by default (see \sitecore\config\<%- appName %>.config).
+ *
+ * The `EditingRenderMiddleware` will
+ *  1. Extract editing data from the Experience Editor POST request
+ *  2. Stash this data (for later use in the page render request) via the `EditingDataService`, which returns a key for retrieval
+ *  3. Enable Next.js Preview Mode, passing our stashed editing data key as preview data
+ *  4. Invoke the actual page render request, passing along the Preview Mode cookies.
+ *     This allows retrieval of the editing data in preview context (via the `EditingDataService`) - see `SitecorePagePropsFactory`
+ *  5. Return the rendered page HTML to the Sitecore Experience Editor
+ */
+// Bump body size limit (1mb by default) for Experience Editor payload
+// See https://nextjs.org/docs/api-routes/api-middlewares#custom-config
+export const config = {
+  api: {
+    bodyParser: {
+      sizeLimit: '2mb',
+    },
+  },
+};
+// Wire up the EditingRenderMiddleware handler
+const handler = new EditingRenderMiddleware().getHandler();
+export default handler;

package/dist/templates/nextjs/src/temp/.gitignore ADDED Viewed

@@ -0,0 +1,3 @@
+*
+!.gitignore
+!GraphQLIntrospectionResult.json