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: Push devDepenencies and mark private #453

Merged
merged 1 commit into from
Jan 7, 2021

Conversation

nschonni
Copy link
Contributor

@nschonni nschonni commented Dec 19, 2020

Since this is currently all content, I don't think the difference between devDependencies and dependencies is a big deal. Also marked private since it's not a published package

@nschonni nschonni requested a review from peterbe as a code owner December 19, 2020 03:27
@nschonni nschonni force-pushed the package-clean branch 2 times, most recently from 246c6fb to 3c12952 Compare December 22, 2020 07:27
@nschonni nschonni force-pushed the package-clean branch 3 times, most recently from e44923a to 6ac6eaf Compare January 5, 2021 02:02
@nschonni
Copy link
Contributor Author

nschonni commented Jan 5, 2021

@peterbe does this make sense to you or should I close it?

Copy link
Contributor

@peterbe peterbe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right. We'll never ship this to npmjs.com as a npm package. At least no plans to do so. And if we change our minds on that, we'll need to just do the work to split that up if necessary.

But why devDependencies instead of dependencies?
If you can explain/justify that and fix the merge conflict, I'll all game for this.

@nschonni
Copy link
Contributor Author

nschonni commented Jan 7, 2021

But why devDependencies instead of dependencies?

Because I saw it as more of tools that are used to produce an end output rather than depenencies on an app that is deployed. Could be flipped all to dependencies either, but the current split doesn't make sense because they're all used by the different script exections

Copy link
Contributor

@peterbe peterbe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you could please refrain from using rebase and especially squashing please.
It makes it impossible to see what was amended in follow-up commits.

@peterbe peterbe merged commit 0b09f3d into mdn:main Jan 7, 2021
@nschonni nschonni deleted the package-clean branch January 7, 2021 19:09
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 4, 2022
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.

2 participants