nodejs/nodebestpractices
1
0
Fork 0
mirror of https://github.com/goldbergyoni/nodebestpractices.git synced 2025-10-29 16:46:01 +08:00
Code Issues Packages Projects Releases Wiki Activity

Production practices

Browse Source
This commit is contained in:
Yoni Goldberg
2023-05-10 18:37:10 +03:00
parent 24c207d404
commit f799d88d26
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -271,6 +271,18 @@ my-system
**TL;DR:** Place all reusable modules in a dedicated folder, e.g., "libraries", and underneath each module in its own folder, e.g., "/libraries/logger". Make the module an independent package with its own package.json file to increases the module encapsulation, and allows future publishing to a repository. In a Monorepo setup, modules can be consumed by 'npm linking' to their physical paths, using ts-paths or by publishing and installing from a package manager repository like the npm registry **TL;DR:** Place all reusable modules in a dedicated folder, e.g., "libraries", and underneath each module in its own folder, e.g., "/libraries/logger". Make the module an independent package with its own package.json file to increases the module encapsulation, and allows future publishing to a repository. In a Monorepo setup, modules can be consumed by 'npm linking' to their physical paths, using ts-paths or by publishing and installing from a package manager repository like the npm registry
```bash
my-system
├─ apps (components)
│ ├─ component-a
├─ libraries (generic cross-component functionality)
│ ├─ logger
│ │ ├─ package.json
│ │ ├─ src
│ │ │ ├─ index.js
```
**Otherwise:** Clients of a module might import and get coupled to internal functionality of a module. With a package.json at the root, one can set a package.json.main or package.json.exports to explicitly tell which files and functions are part of the public interface **Otherwise:** Clients of a module might import and get coupled to internal functionality of a module. With a package.json at the root, one can set a package.json.main or package.json.exports to explicitly tell which files and functions are part of the public interface
🔗 [**Read More: Structure by feature**](./sections/projectstructre/wraputilities.md) 🔗 [**Read More: Structure by feature**](./sections/projectstructre/wraputilities.md)