Skip to content
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

Feat/get ready for yarn2 #69

Merged
merged 2 commits into from
May 28, 2020
Merged

Feat/get ready for yarn2 #69

merged 2 commits into from
May 28, 2020

Conversation

dkontorovskyy
Copy link
Contributor

@dkontorovskyy dkontorovskyy commented Apr 28, 2020

What this does

Refactor PR #57 together with @regevbr to enable easier rollout for a yarn v2 support

@dkontorovskyy dkontorovskyy requested a review from a team as a code owner April 28, 2020 09:48
@CLAassistant
Copy link

CLAassistant commented Apr 28, 2020

CLA assistant check
All committers have signed the CLA.

@dkontorovskyy dkontorovskyy self-assigned this Apr 28, 2020
if (lockfile.type !== this.type) {
throw new InvalidUserInputError(
'Unsupported lockfile provided. ' +
'Please provide `package-lock.json`.',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yarn.lock? not package-lock.json

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yarn uses yarn.lock file, not the npm way of package-lock.json

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep think it was wrong then too 😄

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually @gitphill is correct. I now understand the flow better and indeed it should say yarn.lock

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gitphill addressed your comment 😃

lib/parsers/yarn-lock-parse-base.ts Outdated Show resolved Hide resolved
@dkontorovskyy
Copy link
Contributor Author

@gitphill done ✅ Please, take a look again 😃

@dkontorovskyy dkontorovskyy force-pushed the feat/get-ready-for-yarn2 branch 4 times, most recently from 36d4d38 to 7c14431 Compare May 3, 2020 15:52
@lili2311
Copy link
Contributor

#56

@dkontorovskyy dkontorovskyy merged commit 477623e into master May 28, 2020
@dkontorovskyy dkontorovskyy deleted the feat/get-ready-for-yarn2 branch May 28, 2020 07:58
@snyksec
Copy link

snyksec commented May 28, 2020

🎉 This PR is included in version 1.23.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@dkontorovskyy dkontorovskyy restored the feat/get-ready-for-yarn2 branch May 31, 2020 12:15
@dkontorovskyy dkontorovskyy deleted the feat/get-ready-for-yarn2 branch May 31, 2020 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants