-
Notifications
You must be signed in to change notification settings - Fork 0
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: OPS-10968: use Yarn Berry vs. Yarn Classic #51
Conversation
@@ -10,7 +10,7 @@ jobs: | |||
|
|||
strategy: | |||
matrix: | |||
node-version: [14.x, 16.x] | |||
node-version: [18.x, 20.x] |
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.
Using current LTS versions for testing: https://endoflife.date/nodejs
- path: .yarn/plugins/@yarnpkg/plugin-workspace-tools.cjs | ||
spec: "@yarnpkg/plugin-workspace-tools" | ||
yarnPath: .yarn/releases/yarn-3.6.4.cjs | ||
npmPublishAccess: public |
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.
Since this is a publicly available package, we need to specify it. By default, Yarn Berry creates private packages when you use a scope (e.g., @ginger.io
)
"lodash.set": "^4.3.2" | ||
}, | ||
"resolutions": { | ||
"eslint": "7.17.0" |
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.
See jaredpalmer/tsdx#428. tsdx
is a dead project, we should migrate to tsup
.
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
Use Yarn Berry vs. Yarn Classic.