'shared dependencies' in the monorepo architecture for NodeJsFunction

[juaoose]

I'm using the reference architecture for multiple NodeJsFunction's, where we have a package.json for each function, this seems to work but I have the following questions:

1. When doing it like this, I don't only need the root project's package-lock.json, this means I never need to do npm install in the children directories, right?
2. If I were to create a 'shared library' in my mono repo /shared/logging/index.ts that is imported and used by one of the functions (and this shared package has a dependency that one of my functions doesn't need directly) would I need to add that dependency to the functions package.json? Is this pattern discouraged or should I build a layer instead?

.
├── packages
│   ├── shared
│   │   └── logging
│   │    └── index.ts
│   ├── cool-package
│   │   ├── lib
│   │   │   ├── cool-construct.api.ts
│   │   │   ├── cool-construct.auth.ts
│   │   │   └── cool-construct.ts
│   │   ├── package.json # CDK and runtime dependencies for cool-package
│   │   └── tsconfig.json
│   └── super-package
│       ├── lib
│       │   ├── super-construct.handler.ts
│       │   └── super-construct.ts
│       ├── package.json # CDK and runtime dependencies for super-package
│       └── tsconfig.json
├── package-lock.json # single lock file
├── package.json # root dependencies
└── tsconfig.json