The future yarn structure described in issue 3294
project root
├── package.json <-- root config with 'workspaces' property
├── packages
│ └── foobar
│ ├── node_modules <-- ignored by default
│ │ └── foobar2
│ │ └── package.json
│ └── package.json <-- included
└── readme.md
4 directories, 4 files
Or lerna
project root
├── lerna.json <-- lerna!
├── package.json
├── packages
│ └── foobar
│ ├── node_modules <-- ignored by default
│ │ └── foobar2
│ │ └── package.json
│ └── package.json <-- included
└── readme.md
4 directories, 4 files
example usage in this repository
mor run
mor run --in-order --reverse install
mor root-run install
mor exec --in-order --reverse npm install
checks packages with nsp
hoisting with yarn f**s this up??
hasdep [--prod] [--dev] foobar
hasdep [--prod] [--dev] foobar@^2.0
Collection of helper functions used by mor commands.
has external depenendency
turf funker strålende conventional-changelog? testene brekker for meg