Types of workplaces vary across industries and can be inside a building or outdoors. What is a workplace?Ī workplace or place of employment is a location where people perform tasks, jobs and projects for their employer. So for example, if we assume we have the following workspaces whose current version is 1.5.Are you a job seeker? Find jobs. The associated semver range (for any other range type).The corresponding version in the target workspace (if you use *, ^, ~, or a project-relative path).
Workspace definition archive#
When a workspace is packed into an archive (whether it's through yarn pack or one of the publish commands like yarn npm publish), we dynamically replace any workspace: dependency by: Our current recommendation is to use workspace:*, which will almost always do what you expect. Note that the second flavor is experimental and we advise against using it for now, as some details might change in the future.
Workspace definition code#
This is the pillar of the monorepo approach: rather than using the remote packages from the registry, your project packages will be interconnected and will use the code stored within your repository. If the package manager was to resolve a range that a workspace could satisfy, it will prefer the workspace resolution over the remote resolution if possible. We still provide tools to manage dependencies from multiple workspaces at once, but they need to be explicitly used and offer a better integration (for example yarn add can make suggestions for your new dependencies based on what other workspaces use, but you can override them). Doing this allows us to cleanly decouple projects from one another, since you don't have to merge all their dependencies in one huge unmaintainable list. Said another way, we strictly enforce your workspaces dependencies. Only the dependencies depended upon by a workspace can be accessed. Workspaces have two important properties: This requirement got removed with the 2.0 release in order to help standalone projects to progressively adopt workspaces (for example by listing their documentation website as a separate workspace). Worktrees used to be required to be private (ie list "private": true in their package.json). If they're named, other workspaces will be able to properly cross-reference them. Note that because worktrees are defined with an otherwise regular package.json file, they also are valid workspaces themselves. This doesn't matter in the typical workspace setup because there's usually a single worktree defined in the project-level package.json, but if you try to setup nested workspaces then you must make sure that the nested worktree is defined as a valid workspace of its parent worktree (otherwise Yarn won't find its correct parent folder). They must be connected in some way to the project-level package.json file. For example, if you want all folders within the packages folder to be workspaces, just add packages/* to this array. They must declare a workspaces field which is expected to be an array of glob patterns that should be used to locate the workspaces that make up the worktree. What makes them special is that they have the following properties: Worktrees are defined through the traditional package.json files.
0 kommentar(er)
