最新新闻热点事件2022年9月,aso优化{ }贴吧,装饰协会网站源码,网页ui设计图1. 指定发布目标2. 登录npm#xff0c;使用登录名发布包#xff0c;包名命名原则“登录名/包名”#xff0c;或 “包名” 3. 删除某一个版本npm unpublish pvfhv/eslint-config-prettier1.0.1 --force
删除后的版本不能重复使用#xff0c;正式解释#xff1a;
Unfortun…1. 指定发布目标2. 登录npm使用登录名发布包包名命名原则“登录名/包名”或 “包名” 3. 删除某一个版本npm unpublish pvfhv/eslint-config-prettier1.0.1 --force
删除后的版本不能重复使用正式解释
Unfortunately, there is no longer any way to re-use a previously unpublished version of a package in the npm registry. The reason for this is that various systems rely on nameversion being a unique identifier, and start throwing security warnings if the shasum changes.
While this policy is inconvenient in situations like yours, it also closes a very significant potential security vulnerability if any part of the registry infrastructure is ever compromised, without asking humans to keep track of opaque shasums themselves.
For this reason, we recommend bumping the patch version for even the most trivial updates.
