strapi-provider-upload-google-cloud-storage icon indicating copy to clipboard operation
strapi-provider-upload-google-cloud-storage copied to clipboard

Support for latest Node LTS (20)

Open JakobLierman opened this issue 1 year ago • 6 comments

Describe the bug It is not possible to use Node 20 with this package. error @strapi-community/[email protected]: The engine "node" is incompatible with this module. Expected version "^16 || ^18". Got "20.9.0"

To Reproduce Steps to reproduce the behavior:

  1. Use Node 20.
  2. Try to install this package.

Expected behavior Installation succeeds.

Desktop (please complete the following information):

  • OS: macOS 14.0
  • Browser n/a
  • Version n/a

Additional context

  • Node: 20.9.0
  • Yarn: 1.22.19

JakobLierman avatar Nov 17 '23 10:11 JakobLierman

Any plan to fix the plugin or is it abandoned?

galago avatar Dec 07 '23 09:12 galago

Hey, Facing the same issue. Is there any update on it?

rishi0428 avatar Dec 18 '23 20:12 rishi0428

@Lith is this package abandoned? If so, make sure to archive it, so people know they should not use this anymore.

JakobLierman avatar Jan 08 '24 18:01 JakobLierman

@Lith is this package abandoned? If so, make sure to archive it, so people know they should not use this anymore.

@JakobLierman it still works, even with node v20. The incompatibility error is a warning, in fact it works as it should. https://classic.yarnpkg.com/lang/en/docs/cli/install/#toc-yarn-install-ignore-engines

julesrenaud avatar Jan 08 '24 18:01 julesrenaud

@Lith is this package abandoned? If so, make sure to archive it, so people know they should not use this anymore.

@JakobLierman it still works, even with node v20. The incompatibility error is a warning, in fact it works as it should. classic.yarnpkg.com/lang/en/docs/cli/install/#toc-yarn-install-ignore-engines

Agreed, but warnings are there for a reason. yarn install now never shows the same warning for other packages (that might break my code).

Since it doesn't break anything, I can't imagine that the changes to this repo will be very time consuming.

JakobLierman avatar Jan 08 '24 20:01 JakobLierman

@JakobLierman as far as I understand there's very little to do, we would just need for someone else to takeover the repo

julesrenaud avatar Jan 08 '24 22:01 julesrenaud