Suddenly, when building with appflow, the CLI of the dependency_install step was changed

Appflow
1

Hi, I am an appflow basic member.

Suddenly, when building with appflow, the CLI of the dependency_install step was changed.

image
image1059×217 113 KB

To

image
image1366×205 115 KB

The project that operated the dependency of npm is difficult to change at once.

I migrated according to the existing step, but the CLI of the build environment suddenly changed, resulting in a build failure.

How do I change to an existing build CLI?

Please teach me the way.

2

Hi @yjo0512,

Before the dependency_install step, there is a detect_package_manager step that determines what package manager is used in the project. Here is a quick look at the logic for this step:

  • If a yarn.lock file or .yarnrc file exists in the project, the yarn install command will be used.
  • If a package-lock.json or .npmrc file exists in the project, the npm install command will be used.
  • If both yarn and npm are detected in the project, warning text is displayed in the detect_package_manager step.

To resolve an issue where the incorrect install command is used, you will want to review these files in the project and remove the files for the incorrect package manager.

Alternatively you can also use an appflow config file to directly provide the dependency install to be used by Appflow.

If the issue persists please reach out to Appflow support for further assistance. Thanks!

1 Like