Remove yarn.lock from publish files
#76
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was already ignored in `.npmignore` but was still published to npm due to `files` in package.json
|
Is there any timeline on when this can be merged and included in a release? The yarn.lock being included in the released package incorrectly triggers vulnerability scanners. |
|
cc @garycourt |
|
I have complained about this to my poor colleague without knowing it’s your package that’s shipping this. You owe him an apology! 😉 |
|
I think the entire |
|
@garycourt can this be merged? We are also facing issues with vulnerability scanners due to this lock file. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was already ignored in
.npmignorebut was still published to npm due tofilesin package.json