npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@contentstack/cli-cm-import

v1.33.3

Published

Contentstack CLI plugin to import content into stack

Readme

@contentstack/cli-cm-import

It is Contentstack’s CLI plugin to import content in the stack. To learn how to export and import content in Contentstack, refer to the Migration guide.

Licenseit -m

For switching to EU region update the hosts at config/default.js

{
  host:'https://eu-api.contentstack.com/v3',
  cdn: 'https://eu-cdn.contentstack.com/v3',
 ...
}

For switching to AZURE-NA region update the hosts at config/default.js

{
  host:'https://azure-na-api.contentstack.com/v3',
  cdn: 'https://azure-na-cdn.contentstack.com/v3'
 ...
}

For switching to AZURE-EU region update the hosts at config/default.js

{
  host:'https://azure-eu-api.contentstack.com/v3',
  cdn: 'https://azure-eu-cdn.contentstack.com/v3'
 ...
}

Usage

$ npm install -g @contentstack/cli-cm-import
$ csdx COMMAND
running command...
$ csdx (--version)
@contentstack/cli-cm-import/1.33.3 linux-x64 node-v22.22.3
$ csdx --help [COMMAND]
USAGE
  $ csdx COMMAND
...

Commands

csdx cm:stacks:import [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--backup-dir <value>] [--branch <value>] [--import-webhook-status disable|current]

Import content from a stack

USAGE
  $ csdx cm:import cm:stacks:import [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>]
    [--backup-dir <value>] [--branch <value>] [--import-webhook-status disable|current]

FLAGS
  -B, --branch=<value>
      The name of the branch where you want to import your content. If you don't mention the branch name, then by default
      the content will be imported to the main branch.

  -a, --alias=<value>
      The management token of the destination stack where you will import the content.

  -b, --backup-dir=<value>
      [optional] Backup directory name when using specific module.

  -c, --config=<value>
      [optional] The path of the configuration JSON file containing all the options for a single run.

  -d, --data-dir=<value>
      The path or the location in your file system where the content, you intend to import, is stored. For example, -d
      "C:\Users\Name\Desktop\cli\content". If the export folder has branches involved, then the path should point till the
      particular branch. For example, “-d "C:\Users\Name\Desktop\cli\content\branch_name"

  -k, --stack-api-key=<value>
      API Key of the target stack

  -m, --module=<value>
      [optional] Specify the module to import into the target stack. If not specified, the import command will import all
      the modules into the stack. The available modules are assets, content-types, entries, environments, extensions,
      marketplace-apps, global-fields, labels, locales, webhooks, workflows, custom-roles, personalize projects,
      taxonomies, and composable-studio.

  -y, --yes
      [optional] Force override all Marketplace prompts.

  --branch-alias=<value>
      Specify the branch alias where you want to import your content. If not specified, the content is imported into the
      main branch by default.

  --exclude-global-modules
      Excludes the branch-independent module from the import operation.

  --import-webhook-status=<option>
      [default: disable] [default: disable] (optional) This webhook state keeps the same state of webhooks as the source
      stack. <options: disable|current>
      <options: disable|current>

  --personalize-project-name=<value>
      (optional) Provide a unique name for the Personalize project.

  --replace-existing
      Replaces the existing module in the target stack.

  --skip-app-recreation
      (optional) Skips the recreation of private apps if they already exist.

  --skip-assets-publish
      Skips asset publishing during the import process.

  --skip-audit
      Skips the audit fix that occurs during an import operation.

  --skip-entries-publish
      Skips entry publishing during the import process

  --skip-existing
      Skips the module exists warning messages.

DESCRIPTION
  Import content from a stack

ALIASES
  $ csdx cm:import

EXAMPLES
  $ csdx cm:stacks:import --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir>

  $ csdx cm:stacks:import --config <path/of/config/dir>

  $ csdx cm:stacks:import --module <single module name>

  $ csdx cm:stacks:import --module <single module name> --backup-dir <backup dir>

  $ csdx cm:stacks:import --alias <management_token_alias>

  $ csdx cm:stacks:import --alias <management_token_alias> --data-dir <path/of/export/destination/dir>

  $ csdx cm:stacks:import --alias <management_token_alias> --config <path/of/config/file>

  $ csdx cm:stacks:import --branch <branch name>  --yes --skip-audit

csdx cm:stacks:import [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--backup-dir <value>] [--branch <value>] [--import-webhook-status disable|current]

Import content from a stack

USAGE
  $ csdx cm:stacks:import [-c <value>] [-k <value>] [-d <value>] [-a <value>] [--module <value>] [--backup-dir
    <value>] [--branch <value>] [--import-webhook-status disable|current]

FLAGS
  -B, --branch=<value>
      The name of the branch where you want to import your content. If you don't mention the branch name, then by default
      the content will be imported to the main branch.

  -a, --alias=<value>
      The management token of the destination stack where you will import the content.

  -b, --backup-dir=<value>
      [optional] Backup directory name when using specific module.

  -c, --config=<value>
      [optional] The path of the configuration JSON file containing all the options for a single run.

  -d, --data-dir=<value>
      The path or the location in your file system where the content, you intend to import, is stored. For example, -d
      "C:\Users\Name\Desktop\cli\content". If the export folder has branches involved, then the path should point till the
      particular branch. For example, “-d "C:\Users\Name\Desktop\cli\content\branch_name"

  -k, --stack-api-key=<value>
      API Key of the target stack

  -m, --module=<value>
      [optional] Specify the module to import into the target stack. If not specified, the import command will import all
      the modules into the stack. The available modules are assets, content-types, entries, environments, extensions,
      marketplace-apps, global-fields, labels, locales, webhooks, workflows, custom-roles, personalize projects,
      taxonomies, and composable-studio.

  -y, --yes
      [optional] Force override all Marketplace prompts.

  --branch-alias=<value>
      Specify the branch alias where you want to import your content. If not specified, the content is imported into the
      main branch by default.

  --exclude-global-modules
      Excludes the branch-independent module from the import operation.

  --import-webhook-status=<option>
      [default: disable] [default: disable] (optional) This webhook state keeps the same state of webhooks as the source
      stack. <options: disable|current>
      <options: disable|current>

  --personalize-project-name=<value>
      (optional) Provide a unique name for the Personalize project.

  --replace-existing
      Replaces the existing module in the target stack.

  --skip-app-recreation
      (optional) Skips the recreation of private apps if they already exist.

  --skip-assets-publish
      Skips asset publishing during the import process.

  --skip-audit
      Skips the audit fix that occurs during an import operation.

  --skip-entries-publish
      Skips entry publishing during the import process

  --skip-existing
      Skips the module exists warning messages.

DESCRIPTION
  Import content from a stack

ALIASES
  $ csdx cm:import

EXAMPLES
  $ csdx cm:stacks:import --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir>

  $ csdx cm:stacks:import --config <path/of/config/dir>

  $ csdx cm:stacks:import --module <single module name>

  $ csdx cm:stacks:import --module <single module name> --backup-dir <backup dir>

  $ csdx cm:stacks:import --alias <management_token_alias>

  $ csdx cm:stacks:import --alias <management_token_alias> --data-dir <path/of/export/destination/dir>

  $ csdx cm:stacks:import --alias <management_token_alias> --config <path/of/config/file>

  $ csdx cm:stacks:import --branch <branch name>  --yes --skip-audit

See code: src/commands/cm/stacks/import.ts