cnpm / bug-versions Goto Github PK

View Code? Open in Web Editor NEW

81.0 81.0 194.0 332 KB

collect all bug versions on npm package.

License: Other

JavaScript 100.00%

bug-versions's Introduction

cnpm

cnpm: npm client for npmmirror.com

Requirements

	Minimum	Recommended
Node.js	14.18.0	LTS

Install

npm install cnpm -g

If you're in China, maybe you should install it from our China mirror:

npm install cnpm -g --registry=https://registry.npmmirror.com

Usage

Support all commands just like npm.

Sync packages from `npm`

cnpm sync [moduleName]

Open package document or git web url

cnpm doc [name]
cnpm doc -g [name] # open git web url directly

Build your own private registry npm cli

npm install cnpm -g

# then alias it
alias mynpm='cnpm --registry=https://registry.npm.example.com \
  --registryweb=https://npm.example.com \
  --userconfig=$HOME/.mynpmrc'

Install with original npm cli

cnpm using npminstall by default. If you don't like symlink mode for node_modules, you can change the installer to original npm. But you will lose the fastest install speed.

cnpm i --by=npm react-native

License

MIT

Contributors

_fengmk2	_dead-horse	_{semantic-release-bot}	_alsotang	_0xflotus	_weakish
_gemwuu	_ibigbug	_qiu8310	_elrrrrrrr	_fossabot	_popomore
_xieren58	_xiaohuoni

This project follows the git-contributor spec, auto updated at Wed Dec 06 2023 21:42:25 GMT+0800.

bug-versions's People

Stargazers

Watchers

bug-versions's Issues

feat: add @types/mime 4.0.0 => 3.0.4

request 2.84.0 & 2.84.1

request 刚刚发布的版本 2.84.x 依赖了 hawk 7.x hawk 7.x 依赖 node v8，导致在非 node v8环境下出现错误。

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

tslib 1.12.0 breaks a lot packages

tslib 发了一个 breaking change 导致了问题，目前已知 typeorm 已经不可用

typeorm/typeorm#6054
microsoft/tslib#103

[email protected] 导致 jar2proxy 挂掉

rt, jar2proxy 里直接 Object.create(customEgg.Application.prototype)，而 timing 没有挂在原型上

alinode-v4.8.2兼容性问题

alinode-v4.8.2在centos7上编译所以在centos6上会报GLIBCXX not found的错误，会通过alinode-v4.8.3来解决该问题，4.8.2导向4.8.0

d3-geo 1.11.7 Rollback 1.11.6

As 1.11.7 changes ， it will default installation d3-array@2
The most basic package, it is difficult to lock the deep dependent version。

But d3-array@1 d3-array@2 is not compatible。

https://github.com/d3/d3-array/releases/tag/v2.0.0

需要支持 range 级别的 bug fix

https://github.com/npm/cli/security/advisories/GHSA-hj9c-8jmm-8c52?utm_campaign=Adventures%20in%20Nodeland&utm_medium=email&utm_source=Revue%20newsletter

The automated release is failing 🚨

🚨 The automated release from the `master` branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Not running from a git repository.

The semantic-release command must be executed from a Git repository.

The current working directory is /__w/bug-versions/bug-versions.

Please verify your CI configuration to make sure the semantic-release command is executed from the root of the cloned repository.

Good luck with your project ✨

Your semantic-release bot 📦🚀

{
  "config": {
    "@mdx-js/mdx": {
      "问题版本": {
        "version": "0.16.0",
        "reason": "0.16.1与0.16.2会导致@mdx-js/loader webpack编译的时候报错，阻塞型问题"
      }
    }
  }
}

cnpm / bug-versions Goto Github PK

bug-versions's Introduction

cnpm

Requirements

Install

Usage

Sync packages from npm

Open package document or git web url

Build your own private registry npm cli

Install with original npm cli

License

Contributors

bug-versions's People

Stargazers

Watchers

Forkers

bug-versions's Issues

🚨 The automated release from the master branch failed. 🚨

Invalid npm token.

🚨 The automated release from the master branch failed. 🚨

Not running from a git repository.

Recommend Projects

Recommend Topics

Recommend Org

Sync packages from `npm`

🚨 The automated release from the `master` branch failed. 🚨

🚨 The automated release from the `master` branch failed. 🚨