@@ -10,10 +10,10 @@ and a single [Git repository](https://github.com/bitwarden/clients).
10
10
11
11
The mono-repository root directory contains three main folders.
12
12
13
- - ` apps ` - Our different application specific code, consists of ` web ` , ` browser ` , ` desktop ` and
13
+ - ` apps ` : Our different application specific code, consists of ` web ` , ` browser ` , ` desktop ` and
14
14
` cli ` .
15
- - ` bitwarden_license ` - Bitwarden Licensed version of the web vault.
16
- - ` libs ` - Shared code between the different applications.
15
+ - ` bitwarden_license ` : Bitwarden Licensed version of the web vault.
16
+ - ` libs ` : Shared code between the different applications.
17
17
18
18
## Libs
19
19
@@ -51,8 +51,8 @@ concerned with bootstrapping the application and consuming and configuring code
51
51
52
52
Any code in the ` apps/ ` that doesn't have a tight coupling with the client can be moved into a lib:
53
53
if an exported member is wholly dependent on other libs but not ` apps/ ` , it can likely be moved to a
54
- lib itself. (More concretely, this bars components that rely on global client-specific CSS, but not
55
- components built with Tailwind and the CL. )
54
+ lib itself. (More concretely, this bars components that rely on global client-specific CSS — but not
55
+ components built with Tailwind and the CL — from being included in a lib )
56
56
57
57
> Having a dedicated library project is a much stronger boundary compared to just separating code
58
58
> into folders, though. Each library has a so-called "public API", represented by an index.ts barrel
@@ -64,7 +64,7 @@ An existing example of this pattern is `@bitwarden/components`:
64
64
65
65
- It is consumed by multiple apps and other libs
66
66
- It manages a clear public and private API boundary through its barrel file
67
- - Code ownership is clear-- the CL team only owns the files within ` libs/components `
67
+ - Code ownership is clear — the CL team only owns the files within ` libs/components `
68
68
- The CL team can make independent decisions around internal folder structure and code style
69
69
70
70
As part of this process, we are also investigating utilizing additional tooling (such as Nx) to make
0 commit comments