-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Use files
in package.json
#57
Conversation
couldn't this just be |
I think being explicit is easier to maintain. If you add a new file that is needed by consumers, you add it to the array. If it's just a JS-file (maybe you decide to use Grunt/Gulp, for instance), then it's not automatically included. As of now, this does not include |
we tried doing that in tar-stream and i kept forgetting to add files to pkg json. tests would still work locally so was hard to catch. |
What about moving the js files needed by the package (except for |
can you whitelist the entire lib folder then? :) |
Yup On Fri, 17 Apr 2015 07:59 Mathias Buus [email protected] wrote:
|
i'd be fine with that 👍 |
Also Use `files` in package.json
@mafintosh Done 😄 |
@mafintosh Make new release please. |
@mafintosh ping |
@LinusU I'd love to see this PR merged. |
Hey, sorry for the late turnaround on this. I'm definitely 👍 on this. I don't think that we should move around the files without a major break though. I've seen That being said, I don't think that we'll add any new files in the foreseeable future, so I would be okay with listing Thanks! edit: oh, and also hmm, I wonder if anyone is using and if we also want to have, |
I haven't used this module in years, feel free to tweak this PR or just start from scratch. It seems I've even deleted my fork at some point 😅 |
Sounds good, thanks for the PR and initiative! |
This avoids installing tests and dotfiles when installing your package