StefanOriginal post
Rank 1: Thread
JavaScript
import { Account, Client, Databases } from "appwrite";
const APPWRITE_ENDPOINT = import.meta.env.VITE_APPWRITE_ENDPOINT;const APPWRITE_PROJECT_ID = import.meta.env.VITE_APPWRITE_PROJECT_ID;const APPWRITE_API_ID = import.meta.env.VITE_APPWRITE_API_KEY;
const client = new Client() .setEndpoint(APPWRITE_ENDPOINT) .setProject(APPWRITE_PROJECT_ID) .setKey(APPWRITE_API_KEY); // This code doesn't work
export const account = new Account(client);export const databases = new Databases(client);Would like to get supported
Summary
Developers are inquiring about adding API keys when initializing the Appwrite client. They express concerns about limitations in the client-side Appwrite, inquire about the benefits of `node-appwrite` vs. `appwrite`, and question transitioning from client-side to server-side. The issue with the `setKey` method not working in the provided code snippet is due to a casing error (should be `setKey` not `setkey`). It is clarified that API keys should not be used client-side. The correct implementation should be corrected as follows:
```js
import { Account, Client, Databases } from "appwrite";
const