keys.js | Easy keybindings for browser applications | Frontend Framework library

You have password protected postgres instance but you are not providing the password.

If there isn't an issue on using function on text/csv file types, then I believe you only need to update your mimetype from text/csv into application/vnd.openxmlformats-officedocument.spreadsheetml.sheet.

I've added some resources/links below that lists other mime types if you need your function to work on them too.

To actually support multiple mime types, you need to dynamically identify the mimetype for each file type. You can do it by either:

• Simple string manipulation (if you see a pattern) or have a conditional statement on each mimetype you want to support (both not recommended)
• Or for universality, like this.

• Microsoft mime types
• Google apps mime types
• IANA mime types
• Python drive uploader

Replace:

Imports can only be at the very top level. They're hoisted (above all other non-import statements), and cannot be in blocks or conditionals.

You'll need something like

I was able to solve this problem by writing the connection to the mongodb like this:

You have to acknowledge that calling the Videos.update API endpoint has to be done as shown below:

Case #1: Not updating snippet.title and snippet.description

You have multiple concurrent promise chains, and some of those can fail independently. You need to consolidate all your logic into one promise chain.

When you tried it in Node.js without Discord.js, you didn't export anything and you simply called gsrun(client) after the authorisation was successful, so it worked fine. The problem is that now you try to use getData without any authorisation. Although you have client.authorize in your code, you never use it.

To solve this, I would make at least two different functions here; one for generating the client and one for the get request itself and export them both.

To generate a client I’d wrap this in a promise. This way I could use async/await later. This function will create a client with the JWT, perform the authorisation, and either resolve with the client or reject the promise depending on the results of client.authorize().

Ok. I just found out what went wrong myself and just thought I'd share with anyone who's got the same problem.

My codes were all correct except Heroku doesn't recognise .env and all the secrets saved in .env file will not be picked by Heroku which I wasn't aware of.

The solution is simply go in 'Setting' (in Heroku dashboard) -> Config Vars -> click 'Reveal Config Vars' -> add 'Key' and 'Value' of your secrets (e.g Key: GOOGLE_CLIENT_ID , Value: 'your API Key') then click 'Add'

You can add multiple key, value pairs as you need.