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

Package publication is blocked for reason can not find path #2160

Closed
windmemory opened this issue Mar 22, 2021 · 4 comments
Closed

Package publication is blocked for reason can not find path #2160

windmemory opened this issue Mar 22, 2021 · 4 comments
Labels

Comments

@windmemory
Copy link
Member

Recent package publication build continuously throw errors like below, which blocks the publication of the new versions.

npm WARN exec The following package was not found and will be installed: version-exists
(node:2039) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
(Use `node --trace-deprecation ...` to show where the warning was created)

    Version 0.59.7 of the module wechaty does not exist!
  
Publishing...
npm ERR! code ERR_INVALID_ARG_TYPE
npm ERR! The "path" argument must be of type string. Received undefined

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2021-03-21T14_47_20_678Z-debug.log

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)

@windmemory windmemory added the bug label Mar 22, 2021
@huan huan closed this as completed in e0d4cd2 Mar 22, 2021
@huan
Copy link
Member

huan commented Mar 22, 2021

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 npm publish finally works again.

Waiting for publishing npm/cli#2865 to NPM, then we will be able to remove this workaround:

  "publishConfig": {
-     "cache": "~/.npm",

su-chang added a commit to su-chang/wechaty that referenced this issue Mar 22, 2021
su-chang added a commit to su-chang/wechaty that referenced this issue Mar 22, 2021
huan pushed a commit that referenced this issue Mar 22, 2021
* fix: #2160

* 0.57.19
@huan huan reopened this Mar 24, 2021
@huan
Copy link
Member

huan commented Mar 24, 2021

Let's keep this open until we real fix this problem by following the upstream fixes.

@huan
Copy link
Member

huan commented Mar 24, 2021

NPM v7.7 released: npm/cli#2922

huan added a commit that referenced this issue Mar 24, 2021
Copy link

dosubot bot commented Nov 16, 2023

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.

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 16, 2023
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 23, 2023
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants