<@U01JVDKASAC> <@U01MV4U2EV9> ^^^^^^^
# help
m
@Frank @thdxr ^^^^^^^
Looks like the
colors
package
Copy code
❯ yarn why colors
yarn why v1.22.17
[1/4] Why do we have the module "colors"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found "colors@1.4.2"
info Reasons this module exists
   - "@aws-cdk#assert#@aws-cdk#cloudformation-diff" depends on it
   - Hoisted from "@aws-cdk#assert#@aws-cdk#cloudformation-diff#colors"
   - Hoisted from "@serverless-stack#cli#aws-cdk#colors"
info Disk size without dependencies: "96KB"
info Disk size with unique dependencies: "96KB"
info Disk size with transitive dependencies: "96KB"
info Number of shared dependencies: 0
Done in 0.56s.
Fix for me was to force the use of
colors@1.4.0
by adding a
resolutions
section to my
package.json
Copy code
"resolutions": {
    "colors": "1.4.0"
}
f
The workaround above is actually the best solution at the moment.
Hey @Michael Wolfenden, yeah it is the colors package indeed.
m
f
Yeah, it’s only been fixed in CDK v2.5.0. We are in the process of migrating CDK to v2. Planning to release that early this week. It will have this fix.
o
Will there be migration steps for existing SST apps to upgrade to CDK v2?
f
Yeah, I will add the steps in the release note.
d
Came to ask the same question about migration steps. Looks like the latest version of SST is already cut over to v2? @Frank I’m guessing you guys consider this a stable version of SST with v2?
f
Got to this kinda late 🙏 It seems fairly stable at this point.