package.json has incompatiable node.js version with shopify-app-remix v4, breaking crypto module

[ElPumpo]

#1201 was not ready for production

Perhaps I am wrong, but it broke my orders created webhook. On my code, I have a const { admin, payload } = await authenticate.webhook(request); code

EDIT

Appears that the package.json of this repo has not updated to reflect shopify-app-remix v4, it requires a newer version of node.js

[ElPumpo]

I've explained this bug here https://community.shopify.com/t/crypto-is-not-defined-on-shopify-app-orders-create/580731

[lizkenyon]

Hi there 👋

In version 4.0 we upgraded the required Node version.

Could you confirm what Node version you are using?

[ElPumpo]

Hey thanks for the follow up.

My package.json

Interesting.
It appears to be set to a span-value, I am assuming that I'm <v20.10.0, is this correct?

[lizkenyon]

Hi! The engines field in your package.json shows what Node versions are required for this project to work, not what version you're currently using.

That field says: "This project needs Node.js version 18.20 or higher, OR 20.10 or higher, OR 21.0.0 or higher"

To check what version you're actually using, run this command in your terminal:
node --version
or
node -v

This will output something like v18.12.0 or v20.14.0 - that's your actual Node version. Your node version could be different in developer and production depending on what you have set up.

[ElPumpo]

Oh, actually good question. Now the prod is running on a Railway+docker deployment. Not sure what it's using. Could you recommend a safe version of Node that I could enforce in my package.json?

[ElPumpo]

Actually, the package.json was initially taken from this repo. So it has to be fixed, too.

[lizkenyon]

Thanks for the flag.

You should be able to use a Node version

  "engines": {
    "node": ">=20.19 <22 || >=22.12"
  },

You can review the breaking changes in version 4 of shopify-app-remix package found here, to see if you are affected by any of the other breaking changes. :)

[ElPumpo]

Thanks for the heads up. Ive renamed the bug, too, so the package.json in this repo can be fixed aswell

[lizkenyon]

This has been resolved.

[ElPumpo]

Awesome!