
I'm having issues with querying User
in node-appwrite
. I've shared my codebase as well.
import { Account, Client, ID, Users } from "node-appwrite";
const APPWRITE_ENDPOINT = import.meta.env.VITE_APPWRITE_ENDPOINT;
const APPWRITE_PROJECT_ID = import.meta.env.VITE_APPWRITE_PROJECT_ID;
const APPWRITE_API_KEY = import.meta.env.VITE_APPWRITE_API_KEY;
const client = new Client()
.setEndpoint(APPWRITE_ENDPOINT)
.setProject(APPWRITE_PROJECT_ID)
.setKey(APPWRITE_API_KEY);
export async function getUserByEmail(email: string) {
const users = new Users(client);
// this is not appreciated way to filter users
const response = await users.list();
const userIndex: number = response.users.findIndex((user) => user.email === email);
// if user email is not found on Users table
if (userIndex !== -1) {
return response.users[userIndex];
} else {
return null;
}
}
export async function verifyUserEmail(email: string) {
const account = new Account(client);
await account.create(ID.unique(), email, "12345");
}
I tried to use Query
in node-appwrite
but every solutions and discussions didn't work for me.
Please let me know if someone has experienced with it.

Are you using the latest node sdk? Appwrite cloud has been upgraded to v1.5.5
and the queries are a bit different in the latest version of appwrite.

the List users endpoint accepts an array of queries that allows you to filter by email. Have you read https://appwrite.io/docs/references/cloud/server-nodejs/users#list?

I tried this but didn't work actually.
const result = await users.list([Query.equal("email", email)]);
Recommended threads
- Unable to create push providers - FCM or...
Currently unable to create a push provider for FCM or APNS.... https://github.com/appwrite/console/issues/2045 When uploading a file... FCM = Valid file retu...
- Stuck in "deleting"
my parent element have relationship that doesnt exist and its stuck in "deleting", i cant delete it gives me error: Collection with the requested ID could not b...
- Help with 409 Error on Relationship Setu...
I ran into a 409 document_already_exists issue. with AppWrite so I tried to debug. Here's what I've set up: Collection A has 3 attributes and a two-way 1-to-m...
