json-stringify-safe | Like JSON.stringify , but does n't throw on circular | JSON Processing library

You will want to read the Dockerfile best practices for the RUN instruction from the Docker docs. Each line in a Dockerfile is an image layer and the state after a RUN instruction is executed command is not always persisted on the next layer.

So the apt-get install -y npm won't affect the build when you run npm install -g ... so you received the error: npm command not found.

Please read the guide and attempt to use this single RUN instruction instead.

Fetch api is pretty easy to use, some look into the documentation will let you ready to go.

As for your actual code I did some updates so you can test the fetch api, here it is:

First problem is solved by changing the requires for getSerialize function to :

I have solved this problem by manually installing the same version of the missing packages as global.

I have solved the problem using node package called Api query params.

here is my code:

This can happen when you "npm install" a dependency to the wrong folder, as I have just realised I did. I have a Vue project in the "src" subdirectory, and an index.js (Firebase cloud function) in the "functions" subdirectory.

Dependencies of the Vue project must be installed with "npm install" in the main directory. In contrast, dependencies of the Firebase cloud function must be installed with "npm install" being run in the "functions" subdirectory. I had accidentally installed the dependency in the main directory, and was breaking my head trying to understand why it was complaining that it couldn't find the dependency (googleapis) until I realised what I had done. The fix was of course to install it in the right place (so it showed up in the right package.json), and uninstall it from the wrong place for neatness.