Anyone else facing version issues with reaction-cli

[irtaza780]

So I have a lot of issues with reaction-cli.
First, reaction-cli installs using npm v14 or v15. Then to install the packages for reaction-backend API project, the required version is 18. To again, run the project, again version v14 or v15 is required since that is what's used to install reaction-cli.

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @reactioncommerce/[email protected].
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist

The following packages are not published on npmjs and cloning these as my own repos cause issues as well:

1. api-plugin-sequences
2. api-plugin-fulfillment
3. api-plugin-fulfillment-type-shipping
4. api-plugin-fulfillment-type-pickup
5. api-plugin-fulfillment-method-shipping-flat-rate
6. api-plugin-fulfillment-method-shipping-dynamic-rate
7. api-plugin-fulfillment-method-pickup-store
8. api-plugin-address-validation-test
9. api-plugin-bull-queue

[rjalili]

I have the same issue. Also, seems Node 18.10 is required which conflicts with the error saying that Node v14 or 15 is needed for setting up the project.

[mongy92]

@irtaza780 did you fix it?

[sat8ndra]

facing same problem of version.

[1two3code]

I struggled with this myself for a few hours until I realized that the "quickstart" documentation is not up to date.
Instead of using the reaction-cli package, just pull the reaction, example-storefront and reaction-admin repositories from this github org: https://github.com/reactioncommerce

1. Install all the stuff
   • pnpm i in the reaction repo
   • yarn in the example-storefront repo
   • npm i in the reaction-admin repo
2. Start all the services (in dev mode)
   • docker compose up -f docker-compose.dev.yml in reaction root directory.
   • npm run start:dev in reaction/apps/reaction directory.
   • yarn start:dev in the example-storefront root directory.
   • npm run start:dev in the reaction-admin root directory.

Hope this helps.

[foobarbecue]

should be docker compose -f docker-compose.dev.yml up

[rjalili]

Thank you so much for this.

…

On Mon, Sep 4, 2023, 12:12 Hans Löfgren ***@***.***> wrote: I struggled with this myself for a few hours until I realized that the "quickstart" documentation *is not up to date*. Instead of using the reaction-cli package, just pull the reaction, example-storefront and reaction-admin repositories from this github org: https://github.com/reactioncommerce 1. Install all the stuff - pnpm i in the reaction repo - yarn in the example-storefront repo - npm i in the reaction-admin repo 2. Start all the services (in dev mode) - docker compose up -f docker-compose.dev.yml in reaction root directory. - npm run start:dev in reaction/apps/reaction directory. - yarn start:dev in the example-storefront root directory. - npm run start:dev in the reaction-admin root directory. Hope this helps. — Reply to this email directly, view it on GitHub <#6857 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACSEKWIHGV3GJTEDMCH4PTXYWSR5ANCNFSM6AAAAAA2MC4H4U> . You are receiving this because you commented.Message ID: ***@***.*** com>

[foobarbecue]

I also found that I had to add link-workspace-packages=true to the .npmrc of the reaction repo .

I also had to set export NODE_OPTIONS=--openssl-legacy-provider for the example app.