Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Remove version field frompackage.json#69

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
per1234 merged 1 commit intoarduino:mainfromper1234:remove-version-field
Mar 21, 2022
Merged

Remove version field frompackage.json#69

per1234 merged 1 commit intoarduino:mainfromper1234:remove-version-field
Mar 21, 2022

Conversation

@per1234
Copy link
Contributor

Theversion field is only needed if the package is to be published. In this project,package.json is used only for management of the dependencies and scripts for internal development.

For this reason, having aversion field in the file is harmful because it increases the effort and complexity of making a release, and also is likely to get out of sync with the true version.

Reference:

https://docs.npmjs.com/cli/v8/configuring-npm/package-json#version

If you don't plan to publish your package, the name and version fields are optional.


This was done last year for thearduino/setup-task action without any ill effects:arduino/setup-task#49

The `version` field is only needed if the package is to be published. In this project, package.json is only used formanage dependencies and scripts for internal development.For this reason, having a `version` field is harmful because it increases the effort and complexity of making a release,and also is likely to get out of sync with the true version.
@per1234per1234 added type: enhancementProposed improvement topic: infrastructureRelated to project infrastructure labelsMar 21, 2022
@per1234per1234 requested a review fromumbynosMarch 21, 2022 13:31
@per1234per1234 self-assigned thisMar 21, 2022
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

1 more reviewer

@umbynosumbynosumbynos approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@per1234per1234

Labels

topic: infrastructureRelated to project infrastructuretype: enhancementProposed improvement

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@per1234@umbynos

[8]ページ先頭

©2009-2025 Movatter.jp