Creating an integration app. Stuck on "Run this command to scaffold your new feature, when it is done a URL will be printed"

monday Apps & Developers
1

Hello everyone. I’m trying to create my first integration app on Monday. I’m following the guide but I got stuck at this point. Any thoughts ?
Nodejs is installed correctly.

npx @mondaydotcomorg/monday-cli scaffold run ./ quickstart-integrations -s aed4c0c12962c9a99ff8e640a86aefb3 -t integration-10041982

Screenshot 2022-09-29 104413
Screenshot 2022-09-29 104413973×514 7.44 KB

Screenshot 2022-09-29 104438
Screenshot 2022-09-29 1044381160×745 52.8 KB

2

Hi @paulosoares!

Thanks for bringing this to our attention. We’re aware of this issue and working toward a fix. In the meantime, please pull the Integration app code from our codebase on Github

3

Hi @alessandra, thanks for helping. I’ve tried to clone and run this project, but it’s also not working.

Screenshot 2022-09-30 095340
Screenshot 2022-09-30 0953401480×762 67 KB

4

Hi @paulosoares,

We’ve introduced a fix for this bug. The command to scaffold the project should be working now! Please let me know if you’re unable to access this project.

5

Hi @alessandra Thanks again. Running the github project through npm run start I got the error that posted before.

6

Hi @paulosoares,

We’re working on a fix for our Integrations project! I’ll follow up with you as soon as we have a fix.

Thank you for your patience.

1 Like
7

Hi @paulosoares!

We’ve introduced a fix for this bug. Would you please let me know if this issue still persists for you?

Thank you!

8

Bug still present , when running

 npx @mondaydotcomorg/monday-cli scaffold run ./ quickstart-integrations

it resolves to

npx: installed 285 in 19.454s
> Starting scaffolding process
> Repository was downloaded successfully
> Copying the directory
> Started injecting data to .env file
> Finished injecting data to .env file
> Installing packages. It can take a few moments
> Node modules were installed successfully
> Running the project

> monday-integration-quickstart@0.0.1 start /home/nikbutler/Projects/TIP_Data/Monday/quickstart-integrations
> npm run stop && npm run server

> monday-integration-quickstart@0.0.1 stop /home/nikbutler/Projects/TIP_Data/Monday/quickstart-integrations
> kill-port 8302
0 process was killed

> monday-integration-quickstart@0.0.1 server /home/nikbutler/Projects/TIP_Data/Monday/quickstart-integrations
> nodemon ./src/app.js
[nodemon] 2.0.19
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): .env src/**/*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node ./src/app.js`
[nodemon] app crashed - waiting for file changes before starting...

At this point the app is hanging. , no url present .

9

Checked my .env to ensure signing secret in place
ran npm install

npm WARN monday-integration-quickstart@0.0.1 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
audited 415 packages in 1.494s

npm start shows

[nodemon] starting `node ./src/app.js`
internal/modules/cjs/loader.js:960
  throw err;
  ^
Error: Cannot find module 'node:net'type or paste code here
10

Looks like we could do with throwing a minimum supported version on the calls,
ensuring im on the LTS for Node resolves this

11

Hello there @RedHack,

Thank you for bringing this into our attention!

I have created a report about it and will update you as soon as I have news from our R&D team :slightly_smiling_face:

Cheers,
Matias

13

Hello again,

I’m glad you could find the solution.

It does look like the correct version of node is the way to go.

Let us know if you encounter any other issues or if you have questions!