# Lambda doesn't find monorepo package in nodejs16

**URL:** <https://forum.serverless.com/t/lambda-doesnt-find-monorepo-package-in-nodejs16/17931>\
**Category:** Serverless Framework\
**Tags:** lambda\
**Created:** [November 24, 2022, 8:07pm UTC](https://forum.serverless.com/t/lambda-doesnt-find-monorepo-package-in-nodejs16/17931 "2022-11-24T20:07:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![beneligrossman](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/beneligrossman/32/7189_2.png) [@beneligrossman](https://forum.serverless.com/u/beneligrossman)\
**Post date:** [November 24, 2022, 8:07pm UTC](https://forum.serverless.com/t/lambda-doesnt-find-monorepo-package-in-nodejs16/17931/1 "2022-11-24T20:07:41Z")

</div>

Hi,  
We have a project of nodejs, written in typescript, the project is built in monorepo structure like this:  
├── node\_modules  
├── package.json  
├── tsconfig.json  
├── app  
| └── app.ts  
| └── node\_modules  
| └── package.json  
| └── tsconfig.json  
├── common  
| └── node\_modules  
| └── package.json  
| └── tsconfig.json  
├── lambdas  
| └── node\_modules  
| └── package.json  
| └── tsconfig.json  
Our app and lambdas are using the common files. For nodejs12 and nodejs14 everything worked fine, but when we upgraded to node16, when we run the lambda in aws we get this error:

```auto
"errorType": "Runtime.ImportModuleError",
"errorMessage": "Error: Cannot find module '../common'

```

We tried many plugins like serverless-plugin-optimize and serverless-package-external without success. Is this a bug or we need a different plugin to recognize the common folder in the lambdas?

---

<div class="post-metadata">

**Author:** ![beneligrossman](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/beneligrossman/32/7189_2.png) [@beneligrossman](https://forum.serverless.com/u/beneligrossman)\
**Post date:** [November 27, 2023, 8:27am UTC](https://forum.serverless.com/t/lambda-doesnt-find-monorepo-package-in-nodejs16/17931/2 "2023-11-27T08:27:02Z")

</div>

Still relevant, does someone has an idea? some workaround?