You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During cdk8s init typescript-app, the compile step currently fails with the following trace:
Found 178 errors.
Error: error during project initialization: Error: Command failed: npm run compile
at checkExecSyncError (node:child_process:826:11)
at execSync (node:child_process:900:15)
at Object.exports.post (/Users/rybickic/.npm/_npx/7ca99055be6fff6e/node_modules/cdk8s-cli/templates/typescript-app/.hooks.sscaff.js:35:3)
at executePostHook (/Users/rybickic/.npm/_npx/7ca99055be6fff6e/node_modules/sscaff/lib/sscaff.js:81:37)
at sscaff (/Users/rybickic/.npm/_npx/7ca99055be6fff6e/node_modules/sscaff/lib/sscaff.js:48:15)
at async Object.handler (/Users/rybickic/.npm/_npx/7ca99055be6fff6e/node_modules/cdk8s-cli/lib/cli/cmds/init.js:51:13)
STDOUT:
undefined
STDERR:
undefined
at Object.handler (/Users/rybickic/.npm/_npx/7ca99055be6fff6e/node_modules/cdk8s-cli/lib/cli/cmds/init.js:55:19)
This issue isn't affecting the AWS CDK CLI because it pins the version of dependencies that users start with. This seems like a good solution, since it allows us to reproduce the project starting state of users during builds.
(If we don't fix this, it will likely be fixed upstream within a few days -- but in general, we want to avoid this issue happening again in the future.)
The text was updated successfully, but these errors were encountered:
Fixes#139
I looked into some other solutions that would install versions of dependencies based on the versions within `cdk8s-cli`'s package.json, but decided against it since it would add more complexity to our scaffolding logic that doesn't provide much benefit.
During
cdk8s init typescript-app
, the compile step currently fails with the following trace:The root cause of this is jestjs/jest#12098.
This issue isn't affecting the AWS CDK CLI because it pins the version of dependencies that users start with. This seems like a good solution, since it allows us to reproduce the project starting state of users during builds.
(If we don't fix this, it will likely be fixed upstream within a few days -- but in general, we want to avoid this issue happening again in the future.)
The text was updated successfully, but these errors were encountered: