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

Able to remove files #9

Open
chrisblossom opened this issue Jun 12, 2019 · 2 comments
Open

Able to remove files #9

chrisblossom opened this issue Jun 12, 2019 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@chrisblossom
Copy link
Owner

For example, able to remove package-lock.json / yarn.lock.

@chrisblossom chrisblossom added this to the 1.0.0 milestone Jun 12, 2019
@chrisblossom chrisblossom added the enhancement New feature or request label Jun 12, 2019
@NetizenAbel
Copy link

@chrisblossom while package-lock.json should be removed, yarn.lock is meant to be there.

@chrisblossom
Copy link
Owner Author

Thanks for the comment! Both package-lock.json and yarn.lock should be used for applications (but only one).

In my opinion, libraries should not use lock files because the end user can (and will) end up with different dependencies since both npm and yarn ignore dependency lock files. So your library can seemingly pass tests, but be broken for end users.

On another subject, have you used @backtrack/core yet? If so, what are your thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants