CDK is updating all the time. Which is great, the tool is expanding, gaining more features. Take a look of the timestamps in their GitHub releases page. I wonder if Matt Coulter find a single weekend to chill.
I once made a quick Proof of Concept and after two days, I updated my current installed version and my PoC simply stopped work. Good grief is all remote these days. And for new projects I always want to use the latest stable version in the docs – but I also get:
And somehow I forgot again and again the command. After tried the usual suspects cdk upgrade, cdk update or cdk --upgrade, I had to research again. One. More. Time. I'm writing to help me remember.
The command to upgrade your CDK version is:
npm install -g aws-cdk@latest
Or if you are a Yarn folk:
yarn global upgrade aws-cdk
#AWSWhishlist: Your buddy Amplify CLI has a amplify upgrade 👀 ... Your move.
Cover photo by Jon Moore on Unsplash. I searched for contructs and this was the best I could find.
Top comments (3)
Upgrade CDK version does not solve problems of outdated dependency services between the aws-cdk.core and other modules. Use following commands to solve the prolbem
How is using Pip going to solve npm related issues?
Thanks! Is a little annoying sometimes!