Closed minkimcello closed 4 years ago
Is the plan to use learn and not yarn workspaces? What's the relative tradeoff?
Is the plan to use learn and not yarn workspaces? What's the relative tradeoff?
@minkimcello my idea was to only use lerna for lerna import
. We shouldn't add it as a dependency unless there are other features that we want to use.
A preview package of this pull request has been published with the tag mk_monorepo-conversion
.
You can try it out by running the following command:
$ npm install microstates@mk_monorepo-conversion
or by updating your package.json to:
{
"microstates": "mk_monorepo-conversion"
}
Generated by :no_entry_sign: dangerJS against 1d7d88d23aec7882e0bd7f00854e6ceb62dc6bd8
Motivation
We're going to consolidate the repositories of the microstates org into this monorepo and transfer ownership to @thefrontside.
Approach
packages/microstates/
(minus the.js
).lerna.json
,package.json
, and.gitignore
.lerna
to import because all the commit history is already here.test
,lint
,coverage
, andcoveralls
but not yet running in a matrix. We will modify as we go or possibly move over to Github Actions to keep all checks on one platform.