Hi Support
After the cloud beta update to 1.4.3, I also upgrade my function to use the latest Appwrite SDK (9.0.0) and also change to use the context instead of req and res. The console keeps shows up these messages, not sure why this will show out. The function still ends completed, just want to make sure am I doing something wrong causing this message keeps showing up.
----------------------------------------------------------------------------
Unsupported logs detected. Use context.log() or context.error() for logging.
----------------------------------------------------------------------------
(node:22) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
----------------------------------------------------------------------------
I have lodash and Appwrite SDK installed for my function, and only have function calls with databases client (databases.getDocument, databases.createDocument, databases.updateDocument, and databases.listDocuments) in my function.
The message is most probably logged internally by node via console.log I guess which the new functions do not suggest. Client side should always use context.log(). You can ignore this for now.
This is fixed on Node: 18.13.0 but the Node used by Cloud is most probably 18.0.0.
Based on this issue, I've created a feature request - https://github.com/appwrite/appwrite/issues/6314
Ok, thanks a lot 😀
Yes, we no longer use console.log for several reasons
- reliability was suspect
- privacy reasons. Some system libraries log by themselves and the logs may contain sensitive information.
Recommended threads
- SELF HOSTING ISSUE, DATA NOT MIGRATING T...
Hey, devs, I recently tried to migrate my cloud instance to a self hosted version but my data is not transferred fully only the table structure is transferred ...
- AppwriteException - Transaction with the...
I am using "node-appwrite" module and I have successfully created transaction id but when passing it to tablesDB.createRow function with some other required dat...
- unlike any other provider, your sites DN...
your nameservers dont work with a funny little CNAME error, which is a weird bug but thats what you get when you try to be the kitchen sink, funny errors.