chore: update package-lock.json after npm install

[kevinbuhmann]

PR Checklist

Please check if your PR fulfills the following requirements:

• [N/A] Tests for the changes have been added (for bug fixes / features)
• [N/A] Docs have been added / updated (for bug fixes / features)
• [N/A] If applicable, have a visual design approval

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[github-actions]

👋 @kevinbuhmann,

• 🙏 The Clarity team thanks you for opening a pull request
• 🎉 The build for this PR has succeeded
• 🔍 The PR is now ready for review
• 🍿 In the meantime, checkout out a preview of this PR
• 🖐 You can always follow up here. If you're a VMware employee, you can also reach us on our internal #clarity-support Slack channel

Thank you,

🤖 Clarity Release Bot

[steve-haar]

What version of node and npm are you using? I can't replicate this?

[ashleyryan]

FWIW, I keep getting this too. I've been meaning to ask you about it - usually I delete the package.lock before committing

[steve-haar]

FWIW, I keep getting this too. I've been meaning to ask you about it - usually I delete the package.lock before committing

Deleting package.lock will likely cause dependencies to update. We probably want to be careful doing this. I wonder if different npm versions are causing minor changes here.

[kevinbuhmann]

What version of node and npm are you using? I can't replicate this?

Node v16.15.0
npm v8.1.0

[kevinbuhmann]

Deleting package.lock will likely cause dependencies to update.

I think Ashley meant that she discards the changes.

[steve-haar]

Deleting package.lock will likely cause dependencies to update.

I think Ashley meant that she discards the changes.

Ah, that makes sense.

[kevinbuhmann]

This isn't happening for me anymore. git clean -fdx fixed it. Updating npm probably had something to do with it also.

[steve-haar]

If you have changes to your lock file and you didn't update any package.json files, then either you have the lock file in a bad state or the last commit left the lock file in a bad state. Here is how to see which scenario you are in:

First, undo your changes to the lock file. Next, run the following: git clean -fxd; nvm use; npm install.

If your lock file changes went away, then you just had a bad lock file somehow and all should be good.

If you still see changes to your lock file after this, that means the last commit didn't properly update the lock file. In this case, we should make a chore commit to update the bad lock file.

If this becomes an issue we can add an automated check to the CI/CD that will prevent merging a PR if the lock file is out of sync.

[github-actions]

Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed PRs after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary.