-
-
Notifications
You must be signed in to change notification settings - Fork 409
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
Packages blocking each other from updating | package.json & packages-lock.json #555
Comments
Thanks for letting me know, you can do a pull request if you want. I'm not quite sure if the main library (wa-automate-nodejs) still working or not because the author is no longer maintaining the library due to a strike from Meta. |
Hey, |
sorryy for thee closee, it wass an accident 😅 |
Hey, |
also, here is the link to the error, the other solouton would be, to write a patch for the request ( not the @cypress/request) package but I dont know how. ? |
Hi.
Thanks for figuring it out. I will check it out later.
…On Fri, Nov 24, 2023, 20:11 Johannes Hummer ***@***.***> wrote:
also, here is the link to the error, the other solouton would be, to write
a patch for the request ( not the @cypress/request) package but I dont know
how. ?
So yea, Thank you for your help @SlavyanDesu
<https://github.com/SlavyanDesu> ,
Johannnes
—
Reply to this email directly, view it on GitHub
<#555 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGXSFIQ233BWFRJZEHTT7JDYGCMJFAVCNFSM6AAAAAA7X2EXXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRVGY2TQNJUGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yea, thx , i kinda solved it, but where , can i configure the "" commands" ? Like the .menu likes |
Pretty sure it's |
No, in the meanwhile i fixed it by manually changing all versions but 200moderatate errors |
Hey there,
Im sorry for my 2nd bug report, but this one is very important, and if this wont get fixed, you cant use the bot.
If you want to install the dependencys (npm install) you get many errors, and npm wants you to do npm audit , npm audit fix, and npm audit fix --force, to repair it, but, and here it comes, the version requirements in the package.json and package-lock.json are blocking each other from installing / fixing them, because some dependencys require a newer version, but since some packages are give for Example "2.3.0" ( i dont think that this exists in the code but its just an example) so npm automaticly downgrades the package again, but sine other packages require a other version, so I guess you get the point. Also the package ""request" is no longer supportet by the maintance, but I think with the right versions of the oter packages (( like the newest of though-cookie, which is one of the best exampels for the downgrading issiue) it shouldnt be a problem.
Please Fix this Problem very soon and reach out to me for (you wont need help because your good) but if you need it with repleacing code parts, just tell me.
Theank you for your help.
Johannes
The text was updated successfully, but these errors were encountered: