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

Remove version from package.json #1405

Merged
merged 1 commit into from Sep 6, 2018
Merged

Remove version from package.json #1405

merged 1 commit into from Sep 6, 2018

Conversation

@swissspidy
Copy link
Collaborator

@swissspidy swissspidy commented Sep 6, 2018

This is similar to #1328 / #1333.

The version field (and actually name too) in package.json is optional if you don't plan to publish your package.

Given that private is set to true in package.json to prevent accidental publication, there's no harm in omitting the version field.

This makes the release process a bit easier and less prone to mistakes when changing the version everywhere.

@westonruter westonruter added this to the v1.0 milestone Sep 6, 2018
@westonruter westonruter merged commit 31b46f6 into develop Sep 6, 2018
2 checks passed
@westonruter westonruter deleted the package-version branch Sep 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants