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

chore: remove test directory & non-existent files from dist #1588

Closed
wants to merge 1 commit into from

Conversation

ydcjeff
Copy link

@ydcjeff ydcjeff commented Nov 10, 2022

Users don't need test in the final package.

@jsumners
Copy link
Member

I know we had a long discussion in #136 and #137 about this topic, but I think we should readdress it. My statements in fastify/skeleton#42 (comment) are being proved here. We routinely ignore (package.json).files and it clearly gets out-of-date. I'd rather we:

  1. have a simple .gitignore
  2. remove (package.json).files
  3. do not add a .npmignore file

@mcollina @davidmarkclements what are your thoughts?

@ydcjeff
Copy link
Author

ydcjeff commented Nov 10, 2022

So are we going to have test in .gitignore (we shouldn't ignore test, right?) or will new .gitignore be created when releasing?

@jsumners
Copy link
Member

So are we going to have test in .gitignore

No. We want it included.

@ydcjeff
Copy link
Author

ydcjeff commented Nov 10, 2022

If we are going to have only .gitignore, test directory will still be included in the final distribution.

@jsumners
Copy link
Member

If we are going to have only .gitignore, test directory will still be included in the final distribution.

Correct. We are fine with that. When we are working on projects and need to dig into why a dependency isn't working as expected, or just need to understand the dependency better, we will read the included test files.

@ydcjeff
Copy link
Author

ydcjeff commented Nov 10, 2022

Yes, I agree with that, but I usually read the source on GitHub, so test files are unnecessary at least for me.

@mcollina
Copy link
Member

Those files are there because we want them there.

Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants