Good article! For the file setup have you looked into Yarn Workspaces (yarnpkg.com/lang/en/docs/workspaces/)... I would consider if your packages grow anymore in number.
Awesome. Thanks for the tip. Did not know about workspaces. Tried and unfortunately found (at least) two Ember packages I'm using that will blow up when using yarn workspaces. Reported and it will hopefully be fixed soon. Then I will create a new article and deprecate this one :)
No problem! yeah, I ran into some churn too while getting a large Ember monorepo transitioned to workspaces. There is a noHoist key you can provide in the root package.json, which will prevent the specified packages getting hoisted to the root of the project. This worked for most of my issues, but it’s not ideal to have this list long.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good article! For the file setup have you looked into Yarn Workspaces (yarnpkg.com/lang/en/docs/workspaces/)... I would consider if your packages grow anymore in number.
Awesome. Thanks for the tip. Did not know about workspaces. Tried and unfortunately found (at least) two Ember packages I'm using that will blow up when using yarn workspaces. Reported and it will hopefully be fixed soon. Then I will create a new article and deprecate this one :)
No problem! yeah, I ran into some churn too while getting a large Ember monorepo transitioned to workspaces. There is a
noHoist
key you can provide in the root package.json, which will prevent the specified packages getting hoisted to the root of the project. This worked for most of my issues, but it’s not ideal to have this list long.