nodeapi

On these lines:

The syntax (request?.baseUrl?.replace) that you are trying to use is called Optional Chaining and it is not supported in older versions of Node. You need to upgrade your Node version to at least v14.

You can find the list of supported platforms and their version here.

Your code looks pretty standard - similar to this code of mine.

The times used should be UTC times, so the preferred resolution is to ensure that the UTC time on the server is correct - eg by running a simple OS command such as date -u in bash.

Note also that there is an option called clockTimestamp that can be passed into the Auth0 library.

This will not help if the server clock is badly wrong though. If an IT administrator runs the server, it is their job to ensure that the system clock is correct.

In order to connect to the atlas, make sure you have whitelisted your IP address. you can find the deleted steps here

I resolve my problem. The solution to my error is I used node.js oldest version and then I used the latest version to solve this.

Referring below link i was able to read the data from cloud using node id concept please refer this link: https://medium.com/android-development-by-danylo/android-wear-shared-storage-for-smartwatch-and-the-phone-7c8777b64238

Short answer is, when you see this error please cross check what your fetch request is like, even with a small case difference mongoose will error out , in my case the following happened..

Upon Checking the fetch request , found that the follow_Id was written as follow_id , in the addFollower method

1. First, move the code flow that deals with each individual user value into its own separate async function.

   • Because of how async functions actually work (as each async function marks the boundary of each async state-machine) it isn't really feasible to do concurrent-async work inside a for statement.

2. Invoke that function from within the for loop.

3. Always prefer === over ==.

4. Use TypeScript. Using async JavaScript without TypeScript is a world of pain because you need to keep track of which functions return Promise vs. those that don't, as well as correctly unwrapping Promise objects.

5. Always, wherever possible, have your own try/catch statement that wraps the entire body of an async function, otherwise you'll have to deal with inconsistencies with how different JS engines and JS code handles thrown exceptions and objects.

You should follow the example given in docs. You are receiving JSON response in string from. Please parse the body object as JSON first and then use the result.