-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implements scoped packages #679
Conversation
5b87e57
to
0866c46
Compare
(Merging to a branch other than |
* Readme package renaming * account: renaming package * block: Migrating to scoped packages * npm package URL * block: updating dependencies to scoped packages * blockchain: migrating to scoped packages * common: migrating to scoped packages * tx: migrating to scoped packages * vm: migrating to scoped packages * account,block: updating badges * vm: updating patch to scoped packages * fix: updating new occurrences of package names * fix: updating new occurrences of package names * fix: rebase re-touching * ci: updating Block ci file
* Readme package renaming * account: renaming package * block: Migrating to scoped packages * npm package URL * block: updating dependencies to scoped packages * blockchain: migrating to scoped packages * common: migrating to scoped packages * tx: migrating to scoped packages * vm: migrating to scoped packages * account,block: updating badges * vm: updating patch to scoped packages * fix: updating new occurrences of package names * fix: updating new occurrences of package names * fix: rebase re-touching * ci: updating Block ci file
* Readme package renaming * account: renaming package * block: Migrating to scoped packages * npm package URL * block: updating dependencies to scoped packages * blockchain: migrating to scoped packages * common: migrating to scoped packages * tx: migrating to scoped packages * vm: migrating to scoped packages * account,block: updating badges * vm: updating patch to scoped packages * fix: updating new occurrences of package names * fix: updating new occurrences of package names * fix: rebase re-touching * ci: updating Block ci file
* Readme package renaming * account: renaming package * block: Migrating to scoped packages * npm package URL * block: updating dependencies to scoped packages * blockchain: migrating to scoped packages * common: migrating to scoped packages * tx: migrating to scoped packages * vm: migrating to scoped packages * account,block: updating badges * vm: updating patch to scoped packages * fix: updating new occurrences of package names * fix: updating new occurrences of package names * fix: rebase re-touching * ci: updating Block ci file downgrading nyc in block
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, sorry, I made the comments accidentally here on the PR and then did the review finalization on the other, so therefore the confusion. Should nevertheless be possible to take the comments from here I suppose. 😄
- run: npx lerna run build --scope @ethereumjs/block --include-dependencies | ||
- run: npx lerna run lint --scope @ethereumjs/block | ||
- run: npx lerna run test:node --scope @ethereumjs/block | ||
- run: npx lerna run test:browser --scope @ethereumjs/block |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are the test commands run in a lerna
context here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is to avoid repetition of working-directory:
property of run:
.
In GH actions, each run
command is executed in a new context. That makes impossible to have: run: cd packages/vm
at the beginning of the script, and run the remaining commands from that directory. GitHub's solution is the working-directory:
property that you have to use for every run:
command.
Lerna allows to run npm scripts straight from the repository root, so we don't need to mingle with cd
or working-directory
code.
On another track, I've been doing some work to improve the developer experience of this monorepo, and these very commands could be replaced by shorter versions as well.
From:
npx lerna bootstrap --scope @ethereumjs/block --ignore-scripts --include-dependencies --no-ci
to:
npm run bootstrap @ethereumjs/block
This PR converts package names to scoped packages at every level of the monorepo project.
Note: It merges to
vm/release-v5
branch.