Hi @lone geyser. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#in api routes how to access folders ect
astral oracleBOT
In Next.js, when you're working with API routes and you want to access files in your project, you should use process.cwd() to get the current working directory. This is because Next.js compiles your code into a separate directory, so __dirname might not return the path you expect. Here's an example of how you can use process.cwd():
import { promises as fs } from 'fs'
import path from 'path'
export async function getStaticProps() {
const dictDirectory = path.join(process.cwd(), 'dict')
const filenames = await fs.readdir(dictDirectory)
// ... rest of your code
}
In this example, process.cwd() returns the directory where Next.js is being executed, which should be the root of your project. Then, path.join(process.cwd(), 'dict') gives you the full path to the dict directory in your project (source (https://nextjs.org/docs/pages/api-reference/functions/get-static-props#reading-files-use-processcwd)).
If you want to access static files, like images, you should put them in a folder called public in the root directory. Files inside public can then be referenced by your code starting from the base URL (/). For example, the file public/avatars/me.png can be viewed by visiting the /avatars/me.png path (source (https://nextjs.org/docs/pages/building-your-application/optimizing/static-assets)).
However, please note that only assets that are in the public directory at build time will be served by Next.js. Files added at request time won't be available (source (https://nextjs.org/docs/pages/building-your-application/optimizing/static-assets)).
If you're deploying your Next.js app on Vercel, you should use process.cwd() to determine the current directory of the Vercel Function instead of using __dirname (source (https://vercel.com/guides/how-can-i-use-files-in-serverless-functions#examples-of-reading-files)).