How to add the root as a managed location?

Expected Behavior

lerna link root’s dependencies to packages’ directories (FAQ.root-package.json)

Current Behavior

It’s not working

Possible Solution

symlink root binary to packages binary with a command. maybe like link-parent-bin

Steps to Reproduce (for bugs)

1. create a monorepo(package.name: monorepo)
2. create a package: lerna create demo
3. install tslint in root dir: npm i -D tslint (I not found lerna command to add packages to root package.json)
4. run lerna bootstrap: lerna bootstrap --hoist
5. check tslint in demo dir: cd packages/demo, npx --no-install tslint -v
6. log not found: tslint

lerna.json

{
  "packages": [
    "packages/*",
    "monorepo" // I also try input: "./", "./package.json", "./monorepo", 
  ],
  "version": "independent"
}

Context

Your Environment

Executable	Version
lerna --version	3.13.1
npm --version	6.4.1
yarn --version	VERSION
node --version	10.10.0

OS	Version
Windows 10	1809

[evocateur]

Yeah, probably should remove that bit from the FAQ.

[alvis]

For anyone who really want to have the root managed but got stuck on having "." in the package list in lerna.json, I found a solution to avoid the postinstall/prepare loop during bootstrap. It is to ignore the root package by lerna bootstrap --ignore <root package name> in your postinstall/prepare life cycle script. It works for me and it hopes it works for you too.