-
Notifications
You must be signed in to change notification settings - Fork 39
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
chore: migrate from NPM to Yarn 3 #50
Conversation
.github/workflows/dapi-grpc.yml
Outdated
@@ -15,6 +15,6 @@ on: | |||
jobs: | |||
dapi-tests: | |||
name: Run DAPI gRPC tests | |||
uses: dashevo/platform/.github/workflows/test.yml@master | |||
uses: dashevo/platform/.github/workflows/test.yml@feat-yarn2 |
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.
I think this needs to change to master
before merge?
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.
Yep!
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.
I think you can't rename it before merge, as master
will have the correct file only after the merge? @shumkov
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.
Yeah, but before we need to make sure that tests are running, which is not a case atm.
.github/workflows/release.yml
Outdated
@@ -49,7 +48,7 @@ jobs: | |||
return (tag.includes('dev') ? `${major}.${minor}-dev` : 'latest'); | |||
|
|||
- name: Publish NPM packages | |||
run: npm publish --workspaces --access public --tag ${{ steps.tag.outputs.result }} | |||
run: yarn npm publish --access public --tag ${{ steps.tag.outputs.result }} |
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.
Will this actually work?
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.
Honestly, I didn't try it yet :)
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.
Now it should work.
README.md
Outdated
- Run `yarn setup` to install dependencies and configure and build all packages | ||
- Run `yarn start` to start the local dev environment built from the sources | ||
- Run `yarn test` to run the whole test suite (note that running tests requires a running node, | ||
so be sure to call `npm start` first). Alternatively, you can run tests for a specific |
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.
yarn start
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.
Thank you. Changed all npm mentions.
# Conflicts: # package-lock.json # packages/dapi/package.json # packages/js-dapi-client/package.json # packages/js-dash-sdk/package.json # packages/js-dpp/package.json # packages/js-drive/package.json # packages/platform-test-suite/package.json # packages/wallet-lib/package.json
Issue being fixed or feature implemented
NPM has many downsides comparing with Yarn
What was done?
How Has This Been Tested?
Manually and with CI
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only