Missing Node Modules / Package.JSON issues / DO Deployment issues

[Kodiak]

Hey Guys,

What did you guys ever figure out with updating Wappler removing installed node-modules and overwriting your package.JSON / package-lock.JSON files?

Error when starting server in node missing module

I had the same issue caused by a Wappler upgrade a few release ago, and solved it by deleting the contents of the Wappler project lib folder and restarting Wappler, this will recreate the contents of the lib folder and add the missing memorystore.js file.

DigitalOcean launches App Platform

I tried a pure plain NodeJS project. Connected to a GitHub repo. When you push to the GitHub repo - it gets auto deployed as digital ocean app. Very easy. This is how the Do apps work - you just connect a GitHub repo to them and you are done! One minor thing was that in my package.json I had to adjust the start script to be: "scripts": { "test": "nyc mocha", "start": "node ./node_modules/nodemon/bin/nodemon.js ./index.js" }, Everything else worked just fine. and on each GitHub pus…

Error Deploying Docker to DigitalOcean "Apps"

“scripts”: { “test”: “nyc mocha”, “start”: “node ./node_modules/nodemon/bin/nodemon.js ./index.js” } add this one and commit, check this one send me your email id, ill check via anydesk

MIgrate outside docker

I’ve done all that already but won’t work. I don’t know why. I keep getting this error: message: “Failed to launch the browser process!\n/opt/node_app/node_modules/puppeteer/.local-chromium/linux-869685/chrome-linux/chrome: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory\n\n\nTROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md\n” stack: “Error: Failed to launch the browser process!\n/op…

I had a project I’ve been building on thats ready for production and this past push I did to GitHub / deploy (Digital Ocean Apps) will not build due to the “Build Error: Non-Zero Exit” (See build below)

NODE MODULES:

• Deleted all that were added via command line
• Package file missing components (probably due to node modules missing
• Tried to delete package / package-lock.json files and let Wappler install with no fix

PACKAGE.JSON

Reinstalled the script below but still no fix.

{`
  "name": "argon_dashboard_wappler",
  "version": "1.1.0",
  "private": true,
  "description": "",
  "main": "index.js",
  "engines": {
    "node": ">=12.13.0"
  },
  "scripts": {
    "test": "nyc mocha",
    "start": "node ./index.js"
  },
  "author": "Wappler",
  "license": "ISC",
  "dependencies": {
    "@aws-sdk/client-s3": "^3.41.0",
    "@aws-sdk/s3-request-presigner": "^3.41.0",
    "@shopify/shopify-api": "^2.0.0",
    "archiver": "^5.3.0",
    "axios": "^0.25.0",
    "compression": "^1.7.4",
    "connect-session-knex": "^2.1.1",
    "cookie-parser": "^1.4.6",
    "cors": "^2.8.5",
    "debug": "^4.3.2",
    "dotenv": "^10.0.0",
    "ejs": "^3.1.6",
    "express": "^4.17.1",
    "express-end": "0.0.8",
    "express-fileupload": "^1.2.1",
    "express-session": "^1.17.2",
    "follow-redirects": "^1.14.5",
    "form-data": "^4.0.0",
    "fs-extra": "^10.0.0",
    "get-pixels": "^3.3.3",
    "image-pixels": "^2.2.2",
    "image-to-base64": "^2.2.0",
    "knex": "^0.95.14",
    "mime-types": "^2.1.34",
    "mysql2": "^2.3.3",
    "node-fetch": "^2.6.7",
    "node-schedule": "^2.0.0",
    "nodemon": "^2.0.15",
    "qs": "^6.10.1",
    "session-file-store": "^1.5.0",
    "sharp": "^0.29.3",
    "shopify-api-node": "^3.8.1",
    "socket.io": "^4.4.0",
    "unzipper": "^0.10.11",
    "uuid": "^8.3.2",
    "argon2": "^0.28.3"
  },
  "nodemonConfig": {
    "watch": [
      "app",
      "lib",
      "views",
      "extensions",
      "tmp/**/restart.txt"
    ],
    "ext": "ejs,js,json"
  }
}

I know others have struggled with this as well and I am trying to figure out how to fix this issue (and prevent moving forward).

Have made significant strides in our code since the past successful deployment so wanted to figure this out without having to recreate everything off of the old working Code base.

Any help would be greatly appreciated and we should start to categorize these into different folders in this forum if possible (EX: Deployment >> Digital Ocean >> Deployment Errors & Solutions.

I rely heavily on the community here to get through these issue so try and report back with my findings when I do so we can all support one another!

[2022-04-22 00:39:17] Restoring metadata for "digitalocean/node:node_modules" from cache

[2022-04-22 00:39:19] Restoring data for "heroku/nodejs-engine:nodejs" from cache

[2022-04-22 00:39:19] Restoring data for "heroku/nodejs-engine:toolbox" from cache

[2022-04-22 00:39:19] Restoring data for "digitalocean/node:node_modules" from cache

[2022-04-22 00:39:23] 

[2022-04-22 00:39:23] => Building app

[2022-04-22 00:39:23] 

[2022-04-22 00:39:23] ---> Node.js Buildpack

[2022-04-22 00:39:24] ---> Installing toolbox

[2022-04-22 00:39:24] ---> Getting Node version

[2022-04-22 00:39:24] ---> Resolving Node version

[2022-04-22 00:39:26] ---> Downloading and extracting Node v18.0.0

[2022-04-22 00:39:42] ---> Parsing package.json

[2022-04-22 00:39:43] Project contains package-lock.json, using npm

[2022-04-22 00:39:43] unable to invoke layer creator

[2022-04-22 00:39:43] checking installed npm version: checking npm version: exit status 1

[2022-04-22 00:39:43] ERROR: failed to build: exit status 1

[2022-04-22 00:39:45] 

[2022-04-22 00:39:45] For documentation on the buildpacks used to build your app, please see:

[2022-04-22 00:39:45] Node.js: https://do.co/apps-buildpack-node

[2022-04-22 00:39:45] 

[2022-04-22 00:39:45] ! Build failed (145)

[]

[SWInfotech]

Hi, Kodiak
I know this is very frustrating when you have done everything correctly and at the end there are some error arises for some reason which you have nothing to do with.

customize the Node version in package.json, i think it will definitely work

“engines”: {
“node”: “14.x”
}

In the first attampt it might fail. Try it 2/3 times to update it on the server and let me know.

[Kodiak]

So I pulled the current running version on the console on DO and it was 17.4 so I set this in the package file and originally it did not fix it…

MY MODIFICATION - WORKS

  "engines": {
    "node": "17.4.0"
  },

I also removed the arrows (see below which maybe fixed the issue?) as it worked after this

Anyone have thoughts on if thats why for others to learn from?

Generated by Wappler Below - DOES NOT WORK

 "engines": {
"node": ">=12.13.0"

},

[George]

Seems something weird is happening on the DO side but can’t see what exactly.

Check their https://do.co/apps-buildpack-node

and maybe contact DO support for more info about the real error.

[Apple]

@Kodiak

checking npm version: exit status 1

npm broken?

[SWInfotech]

बधाई हो, after so much of struggle you are live now.