Gathering detailed insights and metrics for contentful-cli-export
Gathering detailed insights and metrics for contentful-cli-export
Gathering detailed insights and metrics for contentful-cli-export
Gathering detailed insights and metrics for contentful-cli-export
npm install contentful-cli-export
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
1 Stars
45 Commits
1 Forks
2 Watching
1 Branches
1 Contributors
Updated on 27 Aug 2024
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
0%
2
Compared to previous day
Last week
13.3%
17
Compared to previous week
Last month
-52.9%
65
Compared to previous month
Last year
27.7%
1,253
Compared to previous year
11
This tool simplifies exporting data from Contentful to a local json file. It's easier to use than the actual Contentful CLI export and can also be easily integrated into a CI/CD pipeline such as GitLab or GitHub.
Note: This is NOT the official Contentful CLI Export tool. That can be found on GitHub π or NpmJS π
β¨ Features Β· π‘ Installation Β· π Example Β· πΉ Usage Β· π ToDo Β· πΎ Contributors Β· π© AcknowledgmentsΒ· π Collection Β· π License
To use this cli script, you must have Node.js π and npm π installed.
To install it, simply run:
1npm install contentful-cli-export --save
Or, if using yarn π:
1yarn add contentful-cli-export
Similarly, if you are using Bun π, just run:
1bun add contentful-cli-release
node
>= 18.20.0npm
>= 10.5.0contentful-management
>= 11.31.7contentful-export
>= 7.19.146To better use the Contentful CLI Export, it is recommended to put the following values in your .env
/.env.local
file:
1CMS_MANAGEMENT_TOKEN=<management-token> 2CMS_SPACE_ID=<space-id> 3CMS_MAX_ALLOWED_LIMIT=100 4CMS_EXPORT_DIR=export/
However, these values could also be passed as parameters during execution.
You will need to create the CMS_EXPORT_DIR
folder, that will contain all the exports. This folder should stay
preferably in the root of your project. If no folder is specified, a folder export/
will be created automatically
if missing.
The basic command should contain the from
environment we want to export from:
1npx contentful-cli-export --from "<environment-id>"
A more complex export command could be
1npx contentful-cli-export --from "<environment-id>" --space-id"<space-id>" --management-token "<management-token>" --compress
This will export data from the specified environment-id, space-id, and management token, and compress the result into a ZIP file.
This script can be used from the command line and accepts various arguments for customization:
--from
or --environment-id
[MANDATORY]: The environment id from which data will be exported.--space-id
: The Contentful space id.--management-token
or --mt
: The Contentful Management Token.--only-published
: To include only published data.--download-assets
: To include assets in the exported data.--verbose
: Display the progress in new lines, instead of animated UI (useful in CI).--compress
: To compress the result into a ZIP file.--export-dir
: To specify a custom directory for the exported data (default is subdirectory CMS_EXPORT_DIR
or
export/
in your project root). The script will exit if this custom folder doesn't exist.--max-allowed-limit
: Number of entries to fetch at each iteration. Max: 1000
- Recommended: 100
(lower values
fire more API calls, but avoid 'Response too big' error).@fciacchi | @psyvic | @aalduz | @leslyto |
Feel free to open issues or pull requests in our GitHub Repository if you have suggestions or improvements to propose.
I would like to express my gratitude to the following parties:
Thank you to everyone involved!
We produce a bunch of interesting packages for Contentful. You might want to check them out:
This project is licensed under the MIT License
No vulnerabilities found.
No security vulnerabilities found.