[pull] latest from npm:latest - #225

We couldn't find a Contributor License Agreement (CLA) for some of the contributors shown below. All contributors listed must be covered under a CLA for this pull request to be merged.

📝 If you are not currently covered under a CLA, please visit https://cla.developers.google.com/. Once you've signed, follow the "New Contributors" link at the bottom of this page to update this check.

Help! I've signed the CLA, but it's still showing me as unsigned.

Individual signers

• It's possible we don't have your GitHub username. Verify that your existing CLA data is accurate.
• You may not be using the email associated with your CLA in your Git commits. Check that the email set on your git commits matches the email associated with your CLA.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the same email used in your Git commits. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.
• You may have Keep my email address private enabled. Without a visible email address, the CLA cannot be checked. Uncheck it and re-create the offending commit, or have your CLA point of contact add your @users.noreply.github.com address to the CLA group.

ℹ️ Googlers: Go here to view more details and manage scans for this pull request.

🔁 New Contributors: Update this check after signing the CLA by clicking here.