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

files attribute must be specified check #851

Closed
moltar opened this issue Nov 4, 2023 · 3 comments · Fixed by #857 or #856
Closed

files attribute must be specified check #851

moltar opened this issue Nov 4, 2023 · 3 comments · Fixed by #857 or #856

Comments

@moltar
Copy link
Contributor

moltar commented Nov 4, 2023

Trying to understand what is the rationale for this check.

if (!isProd() && !this.pjson.files) this.warn(`files attribute must be specified in ${pjsonPath}`)

I think it is valid to have no files, and it is possible to craft .npmignore in a way that will provide the same functionality in the end.

Is there any particular reason Oclif needs files to be set?

@mdonnalley
Copy link
Contributor

That check was added way back in 2018: oclif/config@cc73cb5

Unfortunately, I'm not sure why it was added. I agree with you that it seems unnecessary, especially since it can be replaced with .npmignore. Feel free to open a PR if you would like to remove it

@moltar
Copy link
Contributor Author

moltar commented Nov 6, 2023

I opened a PR, but it requires CLA, which also requires to auth GH to Salesforce.

Just not something I am interested in at the moment.

Feel free to just use the PR/commit. I thereby grant full permission to that change 😁

@mdonnalley
Copy link
Contributor

Thanks @moltar - I merged into another open PR which I plan to merge in the next day or so. Thanks for the contribution 🏆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants