Good Morning all! SST rocks. With that being sai...
# sst
Good Morning all! SST rocks. With that being said I'm having a slight problem, I was slow to upgrade to SST and CDK v2 apparently. I in doing my upgrade I ran into a problem - i am using the aws-cdk-lib/aws-apigatewayv2 so I need to use the @aws-cdk/aws-apigatewayv2-alpha constructs. Only problem apparently the @aws-cdk/aws-apigatewayv2-alpha@2.7.0-alpha.0 has already been removed from npm
Copy code
npm ERR! 404  '@aws-cdk/api-gatewayv2-alpha@2.7.0-alpha.0' is not in this registry.
which means I need to be running CDK v2.8.0 to use @aws-cdk/api-gatewayv2-alpha@2.8.0-alpha.0 I assume I messed up a step somewhere in the upgrade instructions ... it might be because I update to 0.60.4 first then Seed indicated I needed to to do the upgraded steps from the
Copy code
which I did but I never actually ran the npx sst update 0.59.0 I reran the 0.60.4
You messed up package name afaik
The package name is
Copy code
yeah that's where I started - unfortunately it peer dependency is 2.8.0
Copy code
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: test-bed@0.1.0
npm ERR! Found: aws-cdk-lib@2.7.0
npm ERR! node_modules/aws-cdk-lib
npm ERR!   aws-cdk-lib@"2.7.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer aws-cdk-lib@"^2.8.0" from @aws-cdk/aws-apigatewayv2-alpha@2.8.0-alpha.0
npm ERR! node_modules/@aws-cdk/aws-apigatewayv2-alpha
npm ERR!   @aws-cdk/aws-apigatewayv2-alpha@"*" from the root project
You need
Copy code
"@aws-cdk/aws-apigatewayv2-alpha": "2.7.0-alpha.0",
    "@aws-cdk/aws-apigatewayv2-authorizers-alpha": "2.7.0-alpha.0",
Copy code
"aws-cdk-lib": "2.7.0",
npm i --save-exact
thanks Ross, had to jump on a staff meeting, still had no luck so I went the nuclear option - I just built a new sst project, moved my code over and i'm back up and running. Somehow I dinged something, I could see the sst update was indicating that it updated the modules but no. I saw that serverless-stack module had the copies of the 2.7.0 node modules in sources so I assume the update script is trying to load those outside of package manager - but that is an assumption without any knowledge
Thanks @Ross Coundon!
@Gregory Houtteman is it working now? I think the update command is not giving the right recommendations sometimes, and I’m looking into that rn.
yeah @Frank I got it all set and running - sorry for the late reply