“We save millions of dollars for every subsidiary we onboard, because Amazon WorkSpaces can be deployed in many different regions and the solution circumvents the need for physical logistics like shipping hardware and the buildout of network connections. Overall, Amazon WorkSpaces is expected to contribute to an annual savings of more than $17 million for Amazon across all use cases.”
'Amazon WorkSpaces easily accommodated our real-time customer communication and contact channels allowing 100% of our workforce and new employees to be WFH, accelerating our BYOD (Bring Your Own Device) strategy. GrubHub now has the flexibility to control cost and scale this virtual desktop environment to meet the current needs and future needs of our customers, restaurant partners, and drivers for whatever comes next.'
“MAXIMUS uses VDI for several different types of projects, including call centers and for remote users. MAXIMUS is currently going through a move to AWS for all IT services, so it was natural that we utilize WorkSpaces to replace our VDI infrastructure. We were having many issues with VDI backend server support, non-persistent workstations, and many complaints from users about software configurations. With WorkSpaces, we were able to release ourselves from all of the backend maintenance and concentrate on the user experience.”
[email protected]
is linked into bar
if bar
has 'foo': '^1.0.0'
in dependencies.But if bar
has 'foo': '2.0.0'
in dependencies and [email protected]
is not in the workspace then[email protected]
will be installed from the registry. This behavior introduces some uncertainty.workspace:
protocol (same as in Yarn v2). When this protocol is used pnpm will refuseto resolve to anything else than a local workspace package. So if you set 'foo': 'workspace:2.0.0'
installationwill fail telling that no '[email protected]'
is present in the workspace.false
.In that case, pnpm will only link packages from the workspace if the workspace:
protocol is used.pnpm pack
or one of the publish commands like pnpm publish
), we dynamically replace any workspace:
dependency by:*
)1.5.0
, the following:true
, locally available packages are linked to node_modules
instead of being downloaded from the registry.This is very convenient in a monorepo. If you need local packages also be linked to subdependencies, you can use the deep
setting (since v5).false
, packages are downloaded and installed from the registry. However, workspace packages can still be linked by using the workspace:
range protocol. e.g. pnpm add batman@workspace:*
.npmrc
file in the root of your monorepo with the following content:pnpm-workspace.yaml
file with the following content:pnpm recursive install
.shared-workspace-shrinkwrap
)true
, pnpm creates a single pnpm-lock.yaml
file in the root of the workspace (in the directory that contains the pnpm-workspace.yaml
file).A shared lockfile also means that all dependencies of all workspace packages will be in a single node_modules
.node_modules
, packages will have access only to those dependenciesthat are declared in their package.json
. So pnpm's strictness is preserved.false
, if the tooling in your repository does not understand the workspace protocol.