---
title: "Upgrade Content SDK 1.0.0 Next.js apps to version 1.1.0"
slug: "upgrade-content-sdk-1-0-0-next-js-apps-to-version-1-1-0"
abstract: "How to upgrade your Content SDK 1.0.0 Next.js apps to version 1.1.0 to get the latest features and improvements."
---
# Upgrade Content SDK 1.0.0 Next.js apps to version 1.1.0

This guide covers the required changes you must make to your existing Content SDK 1.0.0 applications to take advantage of the new features and improvements in version 1.1.0. Content SDK 1.1 includes enablers for the Design studio (including [import map](https://doc.sitecore.com/sai/en/developers/content-sdk/10/understanding-import-maps.html "Understanding import maps") support), [updates to ESLint](https://doc.sitecore.com/sai/en/developers/content-sdk/10/update-eslint-to-version-9.html "Update ESLint to version 9"), [optimizations to the preview and editing render modes](https://doc.sitecore.com/sai/en/developers/content-sdk/10/editing-and-preview-render-optimization.html "Editing and preview render optimization"), [Cursor rules](https://doc.sitecore.com/sai/en/developers/content-sdk/10/ai-powered-content-sdk-development-using-cursor.html "AI-powered Content SDK development using Cursor"), and more.

Because JavaScript and Next.js development is very flexible and customizable, this guide provides only general instructions and might not cover the specific configurations, custom code, or architectural decisions present in your existing application.

> [!important]
> **Before you begin**
> -   If you have a JSS app that you want to convert into a Content SDK app, follow the migration guide to upgrade your [JSS Next.js 22.9 app to a Content SDK 1.1](https://doc.sitecore.com/sai/en/developers/content-sdk/10/upgrade-jss-22-9-next-js-apps-to-content-sdk-1-1.html "Upgrade JSS 22.9 Next.js apps to Content SDK 1.1") app instead of this topic.
>
> -   Review the [changelog](https://github.com/Sitecore/content-sdk/blob/dev/CHANGELOG.md#110). If your application is heavily customized, the changelog can provide guidance on what additional changes you need that are not covered in this topic.

This topic describes how to:

1. [Update application dependencies in your existing app](https://doc.sitecore.com/sai/en/developers/content-sdk/10/upgrade-content-sdk-1-0-0-next-js-apps-to-version-1-1-0.html#UUID-152a55a9-bd22-41f5-d0cf-4bac5dcdab25_section-id235125743653682 "Update application dependencies in your existing app")
2. [Update the Next.js template files in your existing app](https://doc.sitecore.com/sai/en/developers/content-sdk/10/upgrade-content-sdk-1-0-0-next-js-apps-to-version-1-1-0.html#UUID-152a55a9-bd22-41f5-d0cf-4bac5dcdab25_section-id235125743954142 "Update the Next.js template files in your existing app")

## Update application dependencies in your existing app

For your upgraded application to work correctly, you must update dependencies.

To update your dependencies:

1. In your existing application's `package.json` file, update every `@sitecore-content-sdk` package to version `1.1.0`.
2. Install the dependencies with the following command:

    ```shell
    npm install
    ```

## Update the Next.js template files in your existing app

After updating your dependencies, you must synchronize files in your existing application.

To update the Next.js template files:

1. In `sitecore.cli.config.ts`:
    - Find the following import:

        ```ts
        import config from './sitecore.config';
        ```

    - Replace it with the following:

        ```ts
        import scConfig from './sitecore.config';
        ```

    - Find the following import:

        ```ts
        import {
          generateSites,
          generateMetadata,
          extractFiles,
        } from '@sitecore-content-sdk/nextjs/tools';
        ```

    - Replace it with the following:

        ```ts
        import {
          generateSites,
          generateMetadata,
          extractFiles,
          writeImportMap,
        } from '@sitecore-content-sdk/nextjs/tools';
        ```

    - Modify the `build` section to replace instances of `scConfig: config` with `scConfig` and include the `writeImportMap` as shown:

        ```csharp
        build: {
          commands: [
            generateMetadata(),
            generateSites({
              scConfig,
            }),
            extractFiles({
              scConfig,
            }),
            writeImportMap({
              paths: ['src/components'],
              scConfig,
            }),
          ],
        },
        ```

2. In `src/Layout.tsx`:
    - Find the following line:

        ```ts
        const mainClassPageEditing = mode.isEditing ? 'editing-mode' : 'prod-mode';
        ```

    - Add the following immediately after it:

        ```ts
        const importMapDynamic = () => import('.sitecore/import-map');
        ```

    - Add the `loadImportMap` prop to the `DesignLibrary` element as shown:

        ```ts
        <DesignLibrary loadImportMap={importMapDynamic} />
        ```

3. In the `.sitecore` folder, create a file named `import-map.ts` with the following contents:

    ```ts
    import { combineImportEntries, defaultImportEntries } from '@sitecore-content-sdk/nextjs/codegen';

    export default combineImportEntries(defaultImportEntries, []);
    ```

4. In your existing application's `.gitignore` file, add the following entry after `!.sitecore/component-map.ts`:

    ```

    ...
    !.sitecore/import-map.ts
    ```

    > [!note]
    > Since the `import-map.ts` file is automatically regenerated during the build process, it is not mandatory to add it to the `.gitignore` file.

## Next steps

To finalize the upgrade process, make sure you resolve any errors and warnings you encounter. Enable [debug logging for Content SDK](https://doc.sitecore.com/sai/en/developers/content-sdk/10/debug-logging-in-content-sdk-apps.html "Debug logging in Content SDK apps") specific issues to assist you if necessary.

> [!note]
> **Web experiences and experiments**
> If you use Sitecore Personalize web experiences or experiments, after upgrading the Content SDK, start or restart a single experience or experiment (or start a dummy one) in order to republish it and regenerate the `cloud-version.min.js` library. For instructions, see [Start an experience in Sitecore Personalize](https://doc.sitecore.com/personalize/en/users/sitecore-personalize/introduction-to-experiences/managing-experience-status-in-sitecore-personalize/start-an-experience-in-sitecore-personalize.html), or [Start an experiment in Sitecore Personalize](https://doc.sitecore.com/personalize/en/users/sitecore-personalize/introduction-to-experiments-in-sitecore-personalize/managing-experiment-status-in-sitecore-personalize/start-an-experiment-in-sitecore-personalize.html). [Pausing experiments](https://doc.sitecore.com/personalize/en/users/sitecore-personalize/introduction-to-experiments-in-sitecore-personalize/managing-experiment-status-in-sitecore-personalize/pause-an-experiment-in-sitecore-personalize.html) and [experiences](https://doc.sitecore.com/personalize/en/users/sitecore-personalize/introduction-to-experiences/managing-experience-status-in-sitecore-personalize/pause-an-experience-in-sitecore-personalize.html) and restarting them can invalidate test results.