(@aws-cdk/aws-cognito): import 'punycode/'

❓ General Issue

The Question

about “@aws-cdk/aws-cognito/lib/user-pool.ts”. I don’t think punycode’s trailing slash is necessary.

current code

import { toASCII as punycodeEncode } from 'punycode/';

expected code

import { toASCII as punycodeEncode } from 'punycode';

Environment

• CDK CLI Version: v1.100.0
• Module Version:
• Node.js Version:
• OS:
• Language (Version):

Other information

An error occurred when importing ‘@aws-cdk/aws-cognito’ in the Lambda function handler.

Lambda Runtime Error

{
    "errorType": "Runtime.ImportModuleError",
    "errorMessage": "Error: Cannot find module 'punycode/'\nRequire stack:\n- /var/task/index.js\n- /var/runtime/UserFunction.js\n- /var/runtime/index.js",
    ...
}

[danielholmes]

I had this error as well and was able to fix it through some code changes. For me it was an error in my code organisation.

In my case it was to do with mixing devDependencies/cdk code with my runtime lambda code.

e.g. I had some files similar to:

package.json

{
 ...
  "devDependencies": {
    "@aws-cdk/aws-lambda-nodejs": "^1.114.0",
    "@aws-cdk/aws-cognito": "^1.114.0",
    ...
  }
}

users/index.ts

export { default as Construct } from "./construct";
export { default as getViewerResolver } from "./getViewerResolver";

users/construct.ts

import { UserPool } "@aws-cdk/aws-cognito"
// ...

api/construct.ts

// ...
class ApiConstruct extends Construct {
  constructor() {
    //...
    const defaultResolverLambda = new NodejsFunction(
      this,
      "DefaultGraphQlResolver",
      {
        runtime: Runtime.NODEJS_14_X,
        entry: path.join(__dirname, "..", "users", "index.ts"),
        handler: "getViewerResolver"
      }
    );
  }
}

including that users/index.ts file as an entry therefore included the users/construct.ts which tried to include some cdk cognito code which wasn’t part of my runtime dependencies.

So the fix was to make sure my construct/cdk code was completely separate from my runtime lambda code.

[gorjusborg]

Thanks for posting this @danielholmes, I had the same issue.

We had some Custom::Trigger that would run to populate user data on deploy. Unfortunately, the lambda handler was thrown in the same module as some CDK code that was loosely related. This caused esbuild to bundle aws-cdk-lib/aws-cognito in the lambda, which declares a ‘bundledDependency’ on ‘punycode/’, but apparently it isn’t bundled in the cdk v2 library (hence the require).

This popped up on upgrade to CDK v2 after working with CDK v1 with an error like Runtime.ImportModuleError: Error: Cannot find module 'punycode/'.

The answer for me was to isolate the lambda code so that NO CDK code was referenced (even transitively) by module imports.