Shrinkwrap dependencies of testing package

[rix0rrr]

Describe the bug

npm error notarget No matching version found for @aws-sdk/credential-provider-node@3.774.0.

For npm, Python, and Nuget packages, there may be a delay of up to 30 minutes from when a new package version is published to npmjs.com, pypi.org, or nuget.org and when it is available for installation from a CodeArtifact repository. CodeArtifact automatically synchronizes metadata from these two repositories to ensure that the cache is up to date.

https://docs.aws.amazon.com/codeartifact/latest/ug/external-connection-requesting-packages.html

Caused by

"@aws-sdk/client-codeartifact": "^3",

In the package.json of the tests.

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Version

No response

Expected Behavior

Current Behavior

Reproduction Steps

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

Framework Version

No response

Node.js Version

OS

Language

TypeScript

Language Version

No response

Other information

No response

[rix0rrr]

After doing a lot of work, I just figured out that this cannot work right now, because of this:

// This is necessary to make Symbol.dispose and Symbol.asyncDispose accessible
// in Jest worker processes. It will complain about incompatibility during install
// but work in practice all the same.
repoProject.package.addPackageResolutions(
  'jest-environment-node@30.0.0-alpha.7',
  '@jest/environment@30.0.0-alpha.7',
  '@jest/types@30.0.0-alpha.7',
);

This leads to:

Error: Looks like we're trying to force '@jest/types' to version '30.0.0-alpha.7', but the dependency chain is @aws-cdk-testing/cli-integ => jest => @jest/types@^29.6.3. This can never properly work via shrinkwrapping. Try vendoring a patched version of the intermediary dependencies instead.

The comment in the code says:

/**
 * We may sometimes try to adjust a package version to a version that's incompatible with the declared requirement.
 *
 * For example, this recently happened for 'netmask', where the package we
 * depend on has `{ requires: { netmask: '^1.0.6', } }`, but we need to force-substitute in version `2.0.1`.
 *
 * If NPM processes the shrinkwrap and encounters the following situation:
 *
 * ```
 * {
 *   netmask: { version: '2.0.1' },
 *   resolver: {
 *     requires: {
 *       netmask: '^1.0.6'
 *     }
 *   }
 * }
 * ```
 *
 * NPM is going to disregard the shrinkwrap and still give `resolver` its own private
 * copy of netmask `^1.0.6`.
 *
 * We tried overriding the `requires` version, and that works for `npm install` (yay)
 * but if anyone runs `npm ls` afterwards, `npm ls` is going to check the actual source
 * `package.json`s against the actual `node_modules` file tree, and complain that the
 * versions don't match.
 *
 * We run `npm ls` in our tests to make sure our dependency tree is sane, and our customers
 * might too, so this is not a great solution.
 *
 * To cut any discussion short in the future, we're going to detect this situation and
 * tell our future selves that is cannot and will not work, and we should find another
 * solution.
 */

Sooo... looks like we're SoL until Jest 30 stabilizes.