Build Error on Cloned Project - ESLint 404 [Resolved]

Hi there, I cloned my production app to connect the cloned app to a staging database. Launching through AppGyver works, I can use my app fine. The production app builds fine (as of last week) and this new staging app was building fine yesterday. All my components are updated. Today I get this failed build log:

Hey,
Your build for application Dev - Optum CA Regional Landing Pages ended up failing.

We detected at least the following error in the build:

AB version: 1.6.4 COMMAND: /usr/local/lib/node_modules/@appgyver/orchestra-builder/node_modules/rnv/bin/index.jsconfigure -p web -s standalone -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @appgyver/orchestra-template-standalone@4.3.6 --hooks --npxMode FAILED with ERROR: │ [ error ] COMMAND: npx yarn add @rnv/engine-rn-next@0.36.0-canary.13 FAILED with ERROR: error An unexpected error occurred: “https://registry.yarnpkg.com/@types/eslint/-/eslint-8.4.4.tgz: Request failed "404 Not Found"”. info If you think this is a bug, please open a bug report with the information provided in “/tmp/534873-web-229823/yarn-error.log”. info Visit yarn add | Yarn for documentation about this command. Command failed with exit code 1: npx yarn add @rnv/engine-rn-next@0.36.0-canary.13 warning package.json: No license field warning No license field warning @rnv/engine-rn-next > @expo/next-adapter > @expo/webpack-config > webpack > watchpack > watchpack-chokidar2 > chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies error An unexpected error occurred: “https://registry.yarnpkg.com/@types/eslint/-/eslint-8.4.4.tgz: Request failed "404 Not Found"”. yarn add v1.22.17 [1/4] Resolving packages… [2/4] Fetching packages… info If you think this is a bug, please open a bug report with the information provided in “/tmp/534873-web-229823/yarn-error.log”. info Visit yarn add | Yarn for documentation about this command. warning package.json: No license field warning No license field warning @rnv/engine-rn-next > @expo/next-adapter > @expo/webpack-config > webpack > watchpack > watchpack-chokidar2 > chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies warning @rnv/engine-rn-next > @expo/next-adapter > @expo/webpack-config > webpack > watchpack > watchpack-chokidar2 > chokidar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. error An unexpected error occurred: “https://registry.yarnpkg.com/@types/eslint/-/eslint-8.4.4.tgz: Request failed "404 Not Found"”. Error: Command failed with exit code 1: npx yarn add @rnv/engine-rn-next@0.36.0-canary.13 warning package.json: No license field warning No license field warning @rnv/engine-rn-next > @expo/next-adapter > @expo/webpack-config > webpack > watchpack > watchpack-chokidar2 > chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies warning @rnv/engine-rn-next > @expo/next-adapter > @expo/webpack-config > webpack > watchpack > watchpack-chokidar2 > chokidar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. warning @rnv/engine-rn-next > @expo/next-adapter > @expo/webpack-config > webpack > micromatch > snapdragon > source-map-resolve@0.5.3: See GitHub - lydell/source-map-resolve: [DEPRECATED] Resolve the source map and/or sources for a generated file. error An unexpected error occurred: “https://registry.yarnpkg.com/@types/eslint/-/eslint-8.4.4.tgz: Request failed "404 Not Found"”. yarn add v1.22.17 [1/4] Resolving packages… [2/4] Fetching packages… info If you think this is a bug, please open a bug report with the information provided in “/tmp/534873-web-229823/yarn-error.log”. info Visit yarn add | Yarn for documentation about this command. at makeError (/usr/local/lib/node_modules/@appgyver/orchestra-builder/node_modules/execa/lib/error.js:60:11) at handlePromise (/usr/local/lib/node_modules/@appgyver/orchestra-builder/node_modules/execa/index.js:118:26) at processTicksAndRejections (internal/process/task_queues.js:95:5)

https://registry.yarnpkg.com/@types/eslint/-/eslint-8.4.4.tgz is coming back as a 404

I ran a build on the production version and get the same error as well.

Prod: Optum CA Regional Landing Pages
Staging: Dev - Optum CA Regional Landing Pages

I too am getting build errors as of this afternoon.

We detected at least the following error in the build:

AB version: 1.6.4 COMMAND: /usr/local/lib/node_modules/@appgyver/orchestra-builder/node_modules/rnv/bin/index.jsconfigure -p android -s standalone_bundle -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @appgyver/orchestra-template-standalone@4.3.6 --hooks --npxMode FAILED with ERROR: FAILED with ERROR: error An unexpected error occurred: “https://registry.yarnpkg.com/@types/eslint/-/eslint-8.4.4.tgz: Request failed "404 Not Found"”. info If you think this is a bug, please open a bug report with the information provided in “./yarn-error.log”.

They quietly released a Runtime Version: 4.5.7 when you build your project, and now I get queued :slight_smile: Let’s see if it builds and launches

Confirmed this was fixed with the new Runtime Version: 4.5.7