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

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

Open
huntertran opened this issue Mar 3, 2024 · 5 comments
Open

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

huntertran opened this issue Mar 3, 2024 · 5 comments

Comments

@huntertran
Copy link

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

@zhuyinna
Copy link

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

@huntertran
Copy link
Author

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

Check out this commit: 7b45fbb

@zhuyinna
Copy link

zhuyinna commented Mar 23, 2024

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
Copy link

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?

@AlexHaijiaZhu
Copy link

AlexHaijiaZhu commented Apr 12, 2024

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: 0bb658c

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

3 participants