Yarn workspaces and Ember

3

Hi, I wrote that blog post. :grin:

If I’m reading this correctly:

My workspace root is the Ember app and all of the workspaces are subdirectories in lib under the Ember application.

… your project looks like this?

package.json # with "workspaces" config
ember-cli-build.js
app/
lib/
├── some-package/
├── ├──  package.json
├── ├──  index.js
├──  another-package/
├── ├──  package.json
├── ├──  index.js

Yeah, I don’t think that’ll work. The top-level “package” shouldn’t be a real package and generally doesn’t have its own dependencies. You don’t have to nest projects under a “packages” directory, but it’s very common in monorepos like babel so I used that as the example layout in the blog post.

My current project layout looks like this:

package.json
.eslintrc.js # and other dotfiles
team-one/
├──  engine-a/
├── ├──  package.json
├── ├──  index.js
├── ├──  addon/
├──  addon-b/
├── ├──  package.json
├── ├──  index.json
├── ├──  addon/
├── ├──  app/
team-two/
├── ├──  engine-c/
... # more packages
host-application/
├──  package.json
├──  ember-cli-build.js

The top-level package.json is just:

{
  "private": true,
  "workspaces": [
    "host-application",
    "team-one/*",
    "team-two/*"
  ]
}

Hope this helps!

1 Like