A breaking change was introduced after version v2.3.0 of this demostore FE upgraded major versions of React, Node, NextJS and others. This involves some fundamental changes as well as routes / paths for the FE application to work
In order for your demostore to function, you need the following:
- Automation should use latest automation from dc-demostore-automation using the lastest version of dc-demostore-cli
- Latest version of the dc-demostore-core FE from dc-demostore-core
This path assumes that you already have an Amplience Dynamic Content account with content and a deployed URL in Vercel.
- Get latest version of dc-demostore-cli from npm
npm update @amplience/dc-demostore-cli or if you installed globally npm update @amplience/dc-demostore-cli -g
Once updated you can validate you are on the latest version by running the following command and checking that it matches the latest release on this github page:
demostore --version
- Clean your Amplience Dynamic Content account to start from a blank canvas
demostore cleanup -c -a
- Import from latest automation set
demostore import -l
See import for details needed to update your front end
- Update your front end dc-demostore-core to the latest version and deploy using the right environment variables
Deployed versions will continue to work if you are not changing anything.