Open thanhag opened 9 months ago
@thanhag can you show your repo? Or the error that happens in the deploy job?
The deployment also went wrong for me. The deploy
job fails during npm install
.
This is what the log looks like for me:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: comment-worker@0.0.3
npm ERR! Found: eslint-plugin-n@16.6.2
npm ERR! node_modules/eslint-plugin-n
npm ERR! dev eslint-plugin-n@"^16.0.2" from the root project
npm ERR! peer eslint-plugin-n@"^1[5](https://github.com/mocle/comment-worker/actions/runs/7593901463/job/20684848897#step:5:6).0.0 || ^1[6](https://github.com/mocle/comment-worker/actions/runs/7593901463/job/20684848897#step:5:7).0.0 " from eslint-config-standard@17.1.0
npm ERR! node_modules/eslint-config-standard
npm ERR! dev eslint-config-standard@"^17.1.0" from the root project
npm ERR! peer eslint-config-standard@"^17.0.0" from eslint-config-semistandard@17.0.0
npm ERR! node_modules/eslint-config-semistandard
npm ERR! dev eslint-config-semistandard@"^17.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint-plugin-n@"^15.0.0" from eslint-config-semistandard@1[7](https://github.com/mocle/comment-worker/actions/runs/7593901463/job/20684848897#step:5:8).0.0
npm ERR! node_modules/eslint-config-semistandard
npm ERR! dev eslint-config-semistandard@"^17.0.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/runner/.npm/_logs/2024-01-20T10_49_1[8](https://github.com/mocle/comment-worker/actions/runs/7593901463/job/20684848897#step:5:9)_830Z-eresolve-report.txt
Error: Process completed with exit code 1.
I'll fix this in awhile. I'm travelling at the moment so haven't found time to sit down and look into it.
It's likely due to cloudflare updating the action because of previous incompatibilities with certain node package managers.
Thanks. Have a good time.
I have the same problem as @k24w24
.
@k24w24 looks like my pull request to fix this was merged so I suggest you pull and try again. (see https://github.com/zanechua/comment-worker/pull/5)
I deployed the error as shown in the picture. I really don't have much experience in this matter, I just want to have a free comment on a free static page. I've been messing around with Staticman all week and then moved over here and it still doesn't work. Does anyone have any suggestions for me? Thanks