nested package.json in Yarn workspaces

Question

When using yarn workspaces is it possible to have nested package.json files to resolve dependancies for a subset of packages? Avoiding repetition?

where cra are create-react-apps and pkg are packages that these sites consume. e.g.

| /
| - package.json
|---- /sites
|-------- /cra-1
|         - package.json
|-------- /cra-2
|         - package.json
|---- /packages
|     - package.json   // <<---- Extra level here
|-------- /pkg-1
|         - package.json
|-------- /pkg-1
|         - package.json
|-------- /pkg-2
|         - package.json

this would allow us to share common dependancies for our packages... keep them all in sync and up-to-date

Looks like the answer to the similar question: https://stackoverflow.com/a/31774097/7452021 — exxbrain, Oct 28 '19 at 08:26
I dont think that is a valid answer really. Its not using the tool as its intended, its describing a custom script. — AndrewMcLagan, Nov 01 '19 at 01:11

score 0 · Answer 1 · answered Oct 28 '19 at 10:31

This could work with a bash script as well, but try this one out:

var fs = require('fs')
var join = require('path').join
var os = require('os')
var cp = require('child_process')
var resolve = require('path').resolve

// library path
var lib = resolve(__dirname, '../lib/')

fs.readdirSync(lib)
  .forEach(function (mod) {
    var modPath = join(lib, mod)
// ensure path has package.json
if (!fs.existsSync(join(modPath, 'package.json'))) return

// npm binary based on OS
var npmCmd = os.platform().startsWith('win') ? 'npm.cmd' : 'npm'

// install folder
cp.spawn(npmCmd, ['i'], { env: process.env, cwd: modPath, stdio: 'inherit' })
})

You can run a script via npm and main package.json in your root directory. The script will visit every subdirectory and perform npm install.

That sounds fraught with disaster. – AndrewMcLagan Oct 30 '19 at 05:13 — AndrewMcLagan, Oct 30 '19 at 05:13

nested package.json in Yarn workspaces

1 Answers1