Deployment fails with CLI 3.6.1

monday Apps & Developers
,
1

This morning I had to update the apps CLI (Required update available 3.6.1).
So I ran npm i -g @mondaycom/apps-cli.
But now my deployment to monday code fails. The command I use is mapps code:push -i <id>.
How can I fix this? Is there a problem server side?

:heavy_check_mark: Build asset to deploy
:heavy_check_mark: Preparing environment
:heavy_check_mark: Asset uploaded successfully
:heavy_multiplication_x: There was an error building application.
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] npm warn ERESOLVE overriding peer dependency
Step #2: [builder] > Build failed because of webpack errors
Step #2: [builder] failed to build: (error ID: 1a2262f3):
Step #2: [builder] > Build failed because of webpack errors
Step #2: [builder] ERROR: failed to build: exit status 1
Step #2: ERROR: failed to build: executing lifecycle. This may be the result of using an untrusted builder: failed
with status code: 51
ERROR
ERROR: build step 2 “Google Cloud console” failed: step exited with non-zero status: 1

2

The problem seems to be that I’m using the SDK in a client component.
How can I fix this? Should I make a special server component that calls the SDK?

'use client'
import { EnvironmentVariablesManager } from '@mondaycom/apps-sdk';

const env = new EnvironmentVariablesManager({ updateProcessEnv: true });

./node_modules/@google-cloud/pubsub/node_modules/google-auth-library/build/src/auth/filesubjecttokensupplier.js
Module not found: Can’t resolve ‘fs’

Import trace for requested module:
./node_modules/@google-cloud/pubsub/node_modules/google-auth-library/build/src/auth/identitypoolclient.js
./node_modules/@google-cloud/pubsub/node_modules/google-auth-library/build/src/index.js
./node_modules/@google-cloud/pubsub/build/src/pubsub.js
./node_modules/@google-cloud/pubsub/build/src/index.js
./node_modules/@mondaycom/apps-sdk/dist/esm/queue/queue.js
./node_modules/@mondaycom/apps-sdk/dist/esm/queue/index.js
./node_modules/@mondaycom/apps-sdk/dist/esm/index.js
./src/app/components/MyComponent.tsx
./src/app/page.tsx

3

Hello there @ngruson,

Would you be able to please fill this form adding as much information as possible to it (such as account ID, app ID, timestamps, etc.) so that our team can take a look into it?