To simplify the installation process and reduce potential version conflicts, the FastStore CLI (@faststore/cli) package now directly depends on FastStore Core (@faststore/core).
What has changed?
Previously, both @faststore/core and @faststore/cli packages were required dependencies in the package.json file to install and run a FastStore project.
Now, the new @faststore/cli version depends on the @faststore/core package, eliminating the need for an explicit dependency of both in the package.json file, preventing potential version conflicts, and simplifying installation.
What needs to be done?
If the @faststore/cli is already listed in your dependencies, no further action is needed. To check if the package is listed, open your FastStore project in a code editor, go to the package.json file, and check the dependencies property. For example:
If the @faststore/cli is not listed, follow these steps:
Before applying the following changes to your production environment, test them in a local development environment to ensure compatibility and avoid issues with your live store.
- 
Open your FastStore project in a code editor, navigate to the
package.jsonfile, and locate thedependenciesproperty. - 
In the
dependenciesproperty, replace@faststore/corewith@faststore/cli. Before removing the@faststore/core, thedependenciesproperty might look like this:After replacing
@faststore/corewith@faststore/cli, thedependenciesproperty should look like this:Replace for a
@faststore/cliversion equals or greater than3.0.87. The3.0.87is when these package dependencies changes were applied. - 
Still on the
package.jsonfile, remove the@faststore/clifrom thedevDependenciesproperty. After removal, it should look like this: - 
Open the terminal and run
yarnto install the updated dependencies and update youryarn.lockfile. - 
If no errors occur during or after running
yarn, create a pull request with these changes to your remote repository to apply the updates to production. 
If you encounter any errors when updating these dependencies, please open a ticket with VTEX Support.