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
Package publication is blocked for reason can not find path
#2160
Comments
I have just confirmed that we are running into npm/cli#2834 and it has been fixed by npm/cli#2865 because after using the workaround, our Waiting for publishing npm/cli#2865 to NPM, then we will be able to remove this workaround: "publishConfig": {
- "cache": "~/.npm", |
Let's keep this open until we real fix this problem by following the upstream fixes. |
NPM v7.7 released: npm/cli#2922 |
Hi, @windmemory. I'm Dosu, and I'm helping the wechaty team manage their backlog. I wanted to let you know that we are marking this issue as stale. Based on my understanding, the issue you reported is related to the package publication being blocked due to an error with the "wechaty" module and an undefined path argument. It seems that the issue has been confirmed and a workaround has been implemented. The fix has been merged into the npm/cli repository and is awaiting release. It's worth noting that NPM v7.7 has been released, which may include the fix for this issue. Before we proceed, we would like to confirm if this issue is still relevant to the latest version of the wechaty repository. If it is, please let us know by commenting on this issue. Otherwise, feel free to close the issue yourself, or the issue will be automatically closed in 7 days. Thank you for your contribution, and we appreciate your understanding. Let us know if you have any further questions or concerns. |
Recent package publication build continuously throw errors like below, which blocks the publication of the new versions.
Sample build: https://github.com/wechaty/wechaty/runs/2160117164
Maybe we could check the comments below and found some clues for the problem.
tschaub/gh-pages#354 (comment)
The text was updated successfully, but these errors were encountered: