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/yarn lock diff #1625

Merged
merged 3 commits into from Mar 16, 2022
Merged

Feat/yarn lock diff #1625

merged 3 commits into from Mar 16, 2022

Conversation

tlouisse
Copy link
Member

Currently all demos that use ref are broken. No clue howcome.

This tool lets you easily compare all changed dependencies.

By default, it compares current yarn.lock against the latest yarn.lock, but you can specify how many versions it should go back: yarn lock-diff --versions-back 2.

lock-diff

@changeset-bot
Copy link

changeset-bot bot commented Mar 15, 2022

⚠️ No Changeset found

Latest commit: efdb746

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@tlouisse tlouisse force-pushed the feat/yarnLockDiff branch 2 times, most recently from 9005241 to 2b61a54 Compare March 15, 2022 17:05
@tlouisse tlouisse force-pushed the feat/yarnLockDiff branch 3 times, most recently from 3ed859e to 5d07619 Compare March 15, 2022 22:46
@tlouisse tlouisse merged commit 1ae8f16 into master Mar 16, 2022
@tlouisse tlouisse deleted the feat/yarnLockDiff branch March 16, 2022 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants