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.

Sign up for GitHub

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

Jump to bottom

feat(nodejs): add support dependency location for yarn.lock files #3016

Merged
merged 3 commits into from
Oct 25, 2022
Merged

feat(nodejs): add support dependency location for yarn.lock files #3016

merged 3 commits into from
Oct 25, 2022

Conversation

DmitriyLewen
Copy link
Contributor

@DmitriyLewen DmitriyLewen commented Oct 13, 2022 •
edited
Loading

Description

Add support dependency location for yarn.lock files

Related PRs

Checklist

  • I've read the guidelines for contributing to this repository.
  • I've followed the conventions in the PR title.
  • I've added tests that prove my fix is effective or that my feature works.
  • I've updated the documentation with the relevant information (if needed).
  • I've added usage information (if the PR introduces new options)
  • I've included a "before" and "after" example to the description (if the PR is a user interface change).

@DmitriyLewen DmitriyLewen self-assigned this Oct 13, 2022
@DmitriyLewen DmitriyLewen marked this pull request as ready for review October 25, 2022 07:11
@knqyf263 knqyf263 merged commit cbedd71 into main Oct 25, 2022
@knqyf263 knqyf263 deleted the feat/location-yarn-lock branch October 25, 2022 08:19
@knqyf263 knqyf263 added this to the v0.33.0 milestone Oct 25, 2022
@DmitriyLewen DmitriyLewen mentioned this pull request Nov 22, 2022
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@knqyf263 knqyf263 knqyf263 approved these changes

Assignees

@DmitriyLewen DmitriyLewen

Labels
None yet
Projects
None yet
Milestone
v0.33.0
Development

Successfully merging this pull request may close these issues.
2 participants
@DmitriyLewen @knqyf263