I'm trying to deploy my app to Google Clouds App Engine
. It works perfectly as a local instance, but as soon as I upload it to gcloud, it stops working as intended.
I'm creating a bot for discord. Through it, I access discord and youtubes API. Connecting to these seems to work, as the bot comes online after publishing. However, it seems that the music-playing functionality stops working when its running on gcloud. All other functions work as intended. Which is why I'm suspecting that something has gone wrong with some of the packages. Probably related to music or sound.
Question: Is there a way to verify that my node packages have been installed correctly through the cloud Console
or cmd? Or better yet, re-install them.
I have looked at Deploy and run App Engine.
I publish using the cmd-tools and by running: gcloud app deploy
app.yaml:
runtime: nodejs
env: flex
manual_scaling:
instances: 1
package.json:
{
"name": "yup",
"version": "1.0.5",
"description": "bot",
"main": "app.js",
"private": true,
"engines": {
"node": ">=8.11.3"
},
"scripts": {
"start": "node app.js",
"deploy": "gcloud app deploy",
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "Joel",
"license": "ISC",
"dependencies": {
"@types/request": "^2.48.1",
"discord.js": "^11.4.2",
"express": "^4.16.4",
"ffmpeg-binaries": "^4.0.0",
"fs": "0.0.1-security",
"get-youtube-id": "^1.0.1",
"opusscript": "0.0.6",
"request": "^2.88.0",
"youtube-info": "^1.3.2",
"ytdl-core": "^0.29.1",
"ytdl-getinfo": "^1.1.0"
},
"devDependencies": {
"typescript": "^3.3.3333"
}
}
On further inspection, i can see this in the install-logs:
Step #1: npm WARN [email protected] requires a peer of bufferutil@^3.0.3 but none is installed. You must install peer dependencies yourself.
Step #1: npm WARN [email protected] requires a peer of erlpack@discordapp/erlpack but none is installed. You must install peer dependencies yourself.
Step #1: npm WARN [email protected] requires a peer of node-opus@^0.2.7 but none is installed. You must install peer dependencies yourself.
Step #1: npm WARN [email protected] requires a peer of sodium@^2.0.3 but none is installed. You must install peer dependencies yourself.
Step #1: npm WARN [email protected] requires a peer of libsodium-wrappers@^0.7.3 but none is installed. You must install peer dependencies yourself.
Step #1: npm WARN [email protected] requires a peer of uws@^9.14.0 but none is installed. You must install peer dependencies yourself.