This message was deleted.

I’ve read through the docs - https://www.pulumi.com/blog/lambdas-as-lambdas-the-magic-of-simple-serverless-functions/ and a few related issues but the general theme seems to be this should just work

Are there other libraries you’re trying to pull? Could you please share your code?

Have you tried using

require

within the function to import your dependencies? For example: https://github.com/pulumi/examples/blob/master/aws-ts-serverless-datawarehouse/datawarehouse/partitionRegistrar/index.ts#L28

Unfortunately I’m not able to share the actual code but I’m attempting to reuse other internal modules within a lerna repo. I’ve tried

export const handler = async () => {
  const { foo } = await import('@interal/foo');
  ...
};

aws.cloudwatch.onSchedule('FooFunction', 'rate(10 minutes)', handler);

what does the lambda that gets created look like? does it include

@internal/foo

? I also assume you checked that

@internal/foo

does exist in your local

node_modules

?

@high-lamp-12603 can you try to

require

all of your dependencies from within the function instead of using

import

?

Running into the same issue and the only way to fix it is to require inside the function which isn’t ideal. In my case it’s a very simple function that uses

@google-cloud/pubsub

and it’s quite a different way to write code to think to put it within the function.

@faint-table-42725 all dependencies are in the root node_modules

But what about the node_modules local to your pulumi program’s

package.json

? If not, I believe the code that walks the tree to find your modules will stop there. If that’s the case, one thing you could try is using

codePathOptions

Hey @faint-table-42725 thanks for the help. Moving all dependencies including to the same

package.json

did fix the pulumi warnings but resulted in the same lambda bundle with no dependencies. For

codePathOptions

are you suggesting setting

extraIncludePath: $WORKSPACE_ROOT/node_modules

? I tried this but it ends up serializing the entire repos dependencies causing pulumi to hang

Interesting — I’m surprised that moving them locally didn’t work.

the uploaded lambda is invalid because it kept the typescript type references

and there’s a

$WORKSPACE_ROOT/sub/project/node_modules

— the ones you moved would have those dependencies, right?

I have something like

$WORKSPACE_ROOT/
  package.json
  node_modules/
    ...all dependencies
  projects/
    p1/
      package.json
      index.ts

And

Pulumi.yaml

lives in

p1

?

I’ve tried both in

p1

and in the root

I guess the issue is really where

index.ts

lives I think actually.

which doesn’t seem like it will read from the root

package.json

at all

Then, afterward, it will the extraIncludePaths

Yup which leads to a massive bundle in my case

Yeah, sorry 😞

yea but that’s not really maintainable especially with nested dependencies

yeah

well thanks for the help either way!