Locations tree. It starts with the map of location roots and continues as maps of nested directory entries.
Example: Map { '' => children: Map { 'react-apollo' => { children: Map { 'node_modules' => { children: Map { '@apollo' => { children: Map { 'react-hooks' => { children: Map {}, locator: '@apollo/react-hooks:virtual:cf...#npm:3.1.3' } } } } } }, locator: 'react-apollo:virtual:24...#npm:3.1.3' }, }, 'packages/client' => children: Map { 'node_modules' => Map { ... } } ... }
Example: Map { '' => children: Map { 'react-apollo' => { children: Map { 'node_modules' => { children: Map { '@apollo' => { children: Map { 'react-hooks' => { children: Map {}, locator: '@apollo/react-hooks:virtual:cf...#npm:3.1.3' } } } } } }, locator: 'react-apollo:virtual:24...#npm:3.1.3' }, }, 'packages/client' => children: Map { 'node_modules' => Map { ... } } ... }
Synchronizes previous install state with the actual directories available on disk
location tree
bin symlinks map
state file timestamp (this file is written after all node_modules files and directories)
location tree and bin symlinks with modules, unavailable on disk, removed
Generated using TypeDoc
@yarnpkg/plugin-nmThis plugin adds support for installing packages through a
node_modulesfolder.Install
This plugin is included by default in Yarn 2, but is still considered experimental. For this reason, you must enable it manually by adding the following to your
.yarnrc.ymlfile:nodeLinker: node-modulesWord of caution
While they are supported by virtually every tool, installs using the
node_modulesstrategy have various fundamental issues that the default Plug'n'Play installations don't suffer from (for more details, check out our documentation). Carefully consider the pros and cons before enabling this plugin.