Hey folks, I'm using a postConfirmation lamdbajs function, and it seems like when I deploy, imports/require statements don't work and cause an error. Code looks like this:

/* eslint-disable no-console */
const fetch = require('node-fetch');

export async function main(event, context, callback) {
  try {
    // Post user data to elastic

    console.log('posting data to elastic...', process.env.API_URL);

    await fetch(
      `${process.env.API_URL}/users`, {
        method: 'POST',
        headers: {
          'content-type': 'application/json',
        },
        body: JSON.stringify(event),
      },
    )
      .then((res) => res.json()) // expecting a json response
      .then(() => callback(null, event));
  } catch (error) {
    console.log('there was an error', error);
    callback(null, event);
  }
}

It works fine when testing locally, but after running

sst deploy

and trying out the workflow, I noticed this in CloudWatch:

2021-08-16T02:58:40.094Z	51cc72c5-0e44-4b15-8360-66170252a532	INFO	there was an error TypeError: fetch is not a function
    at Runtime.main [as handler] (/var/task/postConfirmation.js:1080:11)
    at Runtime.handleOnce (/var/runtime/Runtime.js:66:25)

So the one module I import is not working. It's definitely in my package.json:

"dependencies": {
    "@aws-cdk/core": "1.111.0",
    "@serverless-stack/cli": "0.38.0",
    "@serverless-stack/resources": "0.38.0",
    "node-fetch": "^2.6.1"
  },

Any thoughts?

Hey @Ilia Reingold, can I see how you are creating the postConfirmation lambda?

Hey @Frank Full code :

import {
  Auth,
  Stack,
} from '@serverless-stack/resources';

export default class MyStack extends Stack {
  constructor(scope, id, props) {
    super(scope, id, props);

    const auth = new Auth(this, 'Auth', {
      cognito: {
        userPool: {
          userPoolName: process.env.POOL_NAME,

          selfSignUpEnabled: true,

          userVerification: {
            emailSubject: 'Verify your email for Condobeaver!',
            emailBody: 'Thanks for signing up to Condobeaver! Your verification code is {####}',
            // emailStyle: cognito.VerificationEmailStyle.CODE,
            smsMessage: 'Thanks for signing up to Condobeaver! Your verification code is {####}',
          },

          standardAttributes: {
            fullname: {
              required: true,
              mutable: false,
            },
          },

          signInAliases: {
            email: true,
          },
        },

        triggers: {
          postConfirmation: 'src/postConfirmation.main',
        },
      },
    });

    // Show the endpoint in the output
    this.addOutputs({
      UserPoolId: auth.cognitoUserPool.userPoolId,
      IdentityPoolId: auth.cognitoCfnIdentityPool.ref,
      UserPoolClientId: auth.cognitoUserPoolClient.userPoolClientId,
    });
  }
}

hmm.. can you run

sst build

, zip up

.build/cdk.out

and DM it to me?

Sure!

oh what do you by build before deploy?

I ran

sst build

then ran

sst deploy

and that time it worked

Hmm..

sst deploy

runs

sst build

internally.

I also figured that sst deploys runs sst build

Sounds good! Thanks Ilia.