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

Module not found: Error: Can't resolve 'https-proxy-agent' #1478

Open
KevinTung opened this issue Feb 11, 2022 · 12 comments
Open

Module not found: Error: Can't resolve 'https-proxy-agent' #1478

KevinTung opened this issue Feb 11, 2022 · 12 comments

Comments

@KevinTung
Copy link
Contributor

My CICD Building phase failed with the following error:

Module not found: Error: Can't resolve 'https-proxy-agent' in '/home/runner/work/wechaty.js.org/wechaty.js.org/docusaurus/node_modules/@redocly/openapi-core/lib/redocly'

I checked StackOverflow and it seems to be the network error

@KevinTung
Copy link
Contributor Author

  • @huan My mid-term PR's CICD passed 3 days ago, and I finished my final blog on the final branch based on sales-mid-term branch. There is only minimal changes (blog+asset) but resulted in a package error. So I really think there is a change in the CICD scripts or source code which resulted in this issue. To make sure it is not caused by me, I created a new branch, test-final, which has the exact same code as sales-mid-term branch and failed the CICD. So I really wish you can help me fix this package dependency error. Thanks!

@huan
Copy link
Member

huan commented Feb 12, 2022

Please contact your mentor, thank you very much.

@KevinTung
Copy link
Contributor Author

@huan I suppose this CICD bug is due to the recent modification in wechaty.js.org. Shouldn't I contact the managers of this repo?

@huan
Copy link
Member

huan commented Feb 12, 2022

Ok, If you believe you ran into CI/CD bug, you can post the problem after you confirm it by following the below steps:

  1. try to reproduce the problem in your local environment by running npm run build, and make sure it works in your local environment. If it passes, then go to 2; If not, you need to figure it out in your local environment;
  2. if you can pass 1 but fail to pass the GitHub actions, please try to reproduce the GitHub actions problem in your local environment, and then provide the reproducible steps in your issue in detail.

Please feel free to let me know if you have more questions.

@KevinTung
Copy link
Contributor Author

Got it, thanks

@KevinTung
Copy link
Contributor Author

@huan I replicated the bug in my local environment. The issue is that the main branch lack the following 3 packages:

  • https-proxy-agent
  • net
  • tls

I installed it in my branch and it now passed the CI/CD. However, I suppose others will face the same issue so the dependency issue needs to be fixed.

@KevinTung
Copy link
Contributor Author

This is my final branch which passed the test.

@huan
Copy link
Member

huan commented Feb 12, 2022

Great to know you have figured the problem out and have a fix for it!

Please update your PR so that it can make your PR pass the tests, then you will be able to move forward wth your mentors.

@KevinTung
Copy link
Contributor Author

@huan Thanks a lot for your comments and suggestions! There's still one remaining question: Will this dependency issue be solved after my PR is merged into the main branch? Or should others solve this issue again?

@huan
Copy link
Member

huan commented Feb 12, 2022

I'm not sure where this problem comes in because our main branch was good before, but it seems that it fails too right now.

I think we can merge the new dependencies if those are the only changes to fix it.

@KevinTung
Copy link
Contributor Author

OK, , please notify me if my PR is merged or if other related patch is merged by you. I will also be aware of this fix too.

@huan
Copy link
Member

huan commented Mar 24, 2022

@KevinTung Please help us to close this issue if it has been solved, thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants