# Using Common Code Across Services (Node JS)

**URL:** <https://forum.serverless.com/t/using-common-code-across-services-node-js/20374>\
**Category:** Serverless Framework\
**Tags:** aws, lambda\
**Created:** [July 25, 2024, 10:11pm UTC](https://forum.serverless.com/t/using-common-code-across-services-node-js/20374 "2024-07-25T22:11:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![threes-was-taken](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/threes-was-taken/32/8074_2.png) [@threes-was-taken](https://forum.serverless.com/u/threes-was-taken)\
**Post date:** [July 26, 2024, 7:32am UTC](https://forum.serverless.com/t/using-common-code-across-services-node-js/20374/2 "2024-07-26T07:32:14Z")

</div>

Hi @johnjohnjohn

I’m not sure I can fully answer your question as I do not have experience with multiple services yet. I’m hoping to help you by referencing [this article on multi-service deployments](https://www.serverless.com/blog/serverless-framework-compose-multi-service-deployments).

I also found [this thread](https://forum.serverless.com/t/folder-structure-for-multiple-servies-with-shared-library/1153/7) that will, hopefully, get you where you need to be 🙂

My guess is that if you combine both ways of working, you’ll be able to package the shared libs and services in one go and be able to reference the shared libs across the services.

Good luck!

---

_[View the full topic](https://forum.serverless.com/t/using-common-code-across-services-node-js/20374)._