hexo-action icon indicating copy to clipboard operation
hexo-action copied to clipboard

Error: Cannot find module 'hexo-util/lib/spawn'

Open huntertran opened this issue 11 months ago • 5 comments

The spawn folder was moved to 'hexo-util/dist/spawn'

huntertran avatar Mar 03 '24 19:03 huntertran

I am still confused how i can do with it ? which config file should I moidfy?

zhuyinna avatar Mar 23 '24 03:03 zhuyinna

I am still confused how i can do with it ? which config file should I moidfy?

Check out this commit: https://github.com/sma11black/hexo-action/pull/28/commits/7b45fbba1ed6bde78f8ed2719ec9b7c0bd49e220

huntertran avatar Mar 23 '24 03:03 huntertran

I have resolve the above problem by usign: sma11black/hexo-action@7b45fbba1ed6bde78f8ed2719ec9b7c0bd49e220

but there is a new error:sma11black/hexo-action@7b45fbba1ed6bde78f8ed2719ec9b7c0bd49e220

do you know how to solve it?

zhuyinna avatar Mar 23 '24 04:03 zhuyinna

I have resolve the above problem by usign: sma11black/hexo-action@7b45fbba1ed6bde78f8ed2719ec9b7c0bd49e220

but there is a new error:sma11black/hexo-action@7b45fbba1ed6bde78f8ed2719ec9b7c0bd49e220

do you know how to solve it?

I guess the possible reason is : The issue you're encountering suggests that although you've configured your GitHub Actions workflow to use Node.js version 20, the sma11black/hexo-action@7b45fbba1ed6bde78f8ed2719ec9b7c0bd49e220 GitHub Action is still using an older Node.js version (12.22.12). This discrepancy is likely due to how the hexo-action is packaged or configured.

Do you have any solutions?

zhuyinna avatar Mar 23 '24 04:03 zhuyinna

I have resolve the above problem by usign: sma11black/hexo-action@7b45fbba1ed6bde78f8ed2719ec9b7c0bd49e220 but there is a new error:sma11black/hexo-action@7b45fbba1ed6bde78f8ed2719ec9b7c0bd49e220 do you know how to solve it?

I guess the possible reason is : The issue you're encountering suggests that although you've configured your GitHub Actions workflow to use Node.js version 20, the 7b45fbb GitHub Action is still using an older Node.js version (12.22.12). This discrepancy is likely due to how the hexo-action is packaged or configured.

Do you have any solutions?

Check this: 0bb658ca730aaee12c5a7a370efda4d5fd0033ac

AlexHaijiaZhu avatar Apr 12 '24 00:04 AlexHaijiaZhu