No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

that's not up to pulumi, is the dependency on your package.json?

make sure it's there, npm install as 'prod' dependency not a dev one

It’s in my package.json yes under dependencies

then the other thing I can think of is that pulumi is not deploying your dependencies.

look if node_modules is in aws

try with

```import AWSXRay from 'aws-xray-sdk-core';```


Using ‘aws-xray-sdk-code’ results in the same problem. I can only see my __index.js in the Code source explorer, unless you are referring to another part of the AWS console

I am defining the lambda from a file, do I have to add the dependencies here explicitly?

```const fn = new aws.lambda.Function('InfraLambda', {
  code: new pulumi.asset.AssetArchive({
    '__index.js': new pulumi.asset.FileAsset('./handler.js'),
  }),
  handler: '__index.handler',
  runtime: aws.lambda.NodeJS12dXRuntime,
  role: role.arn,
  tracingConfig: {
    mode: 'Active', // Enable X-ray
  },
});```

yep you need to also push over the node_modules folder, so that's another asset.

or use webpack to pack only your 'prod' dependencies and then declare the result of the build as an asset

this guy in this post is zipping the whole thing <https://medium.com/swlh/migrating-serverless-to-pulumi-project-7ce798103505>

I am using a library that copies node_modules over to /build folder and I am using that as asset. but I am using typescript so I need to transpile over the files