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
@zkochan we use the aws-cdk which just installs a cmd line tool. Locally this works fine without any global install, it picks it up from the node_modules/.bin folder, but on the CI server for some reason, this doesn't work. The only other way to get it to work is to use npx aws-cdk:
possibly due to the mismatch that the package is called aws-cdk but the executable is called cdk? 🤷♂️
Ideally, we would like to use the same package manager for all tasks to save confusion and hence why we have historically done a global install of the package. It also obviously saves having to prefix every subsequent cdk command as we run several as part of the pipeline.
@zkochan we use the
aws-cdk
which just installs a cmd line tool. Locally this works fine without any global install, it picks it up from the node_modules/.bin folder, but on the CI server for some reason, this doesn't work. The only other way to get it to work is to usenpx aws-cdk
:unfortunately
pnpx aws-cdk
(orpnpm dlx aws-cdk
) doesn't work:possibly due to the mismatch that the package is called
aws-cdk
but the executable is calledcdk
? 🤷♂️Ideally, we would like to use the same package manager for all tasks to save confusion and hence why we have historically done a global install of the package. It also obviously saves having to prefix every subsequent cdk command as we run several as part of the pipeline.
Originally posted by @caveman-dick in #4658 (comment)
The text was updated successfully, but these errors were encountered: