next.js: vercel error no such file or directory, open '/var/task/node_modules/shiki/themes/one-dark-pro.json'

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:19 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T8103
    Binaries:
      Node: 16.16.0
      npm: 9.8.0
      Yarn: 1.22.19
      pnpm: 7.16.0
    Relevant Packages:
      next: 13.4.10
      eslint-config-next: 13.4.10
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

Link to the code that reproduces this issue or a replay of the bug

.

To Reproduce

import { serialize } from 'next-mdx-remote/serialize';
import readingTime from 'reading-time';
import remarkGfm from 'remark-gfm';
import rehypeSlug from 'rehype-slug';
import rehypeAutolinkHeadings from 'rehype-autolink-headings';
import rehypePrettyCode from 'rehype-pretty-code';

/** @type {import('rehype-pretty-code').Options} */
const options = {
    theme: 'one-dark-pro',
    onVisitLine(node: any) {
        if (node.children.length === 0) {
            node.children = [{ type: 'text', value: ' ' }];
        }
    },
    onVisitHighlightedLine(node: any) {
        node.properties.className.push('line--highlighted');
    },
    onVisitHighlightedWord(node: any) {
        node.properties.className = ['word--highlighted'];
    },
};

export async function mdxToHtml(source: any) {
    const mdxSource = await serialize(source, {
        mdxOptions: {
            remarkPlugins: [remarkGfm],
            rehypePlugins: [
                rehypeSlug,
                [rehypePrettyCode, options],
                [
                    rehypeAutolinkHeadings,
                    {
                        properties: {
                            className: ['anchor'],
                        },
                    },
                ],
            ],
            format: 'mdx',
        },
    });

    return {
        html: mdxSource,
        wordCount: source.split(/\s+/gu).length,
        readingTime: readingTime(source).text,
    };
}

got this error in vercel logs while building pages and i am using app router

ENOENT: no such file or directory, open '/var/task/node_modules/shiki/themes/one-dark-pro.json'
and i also install shiki package

Describe the Bug

got this error in vercel logs while building pages and i am using app router

Expected Behavior

mdx

Which browser are you using? (if relevant)

brave

How are you deploying your application? (if relevant)

Vercel

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 5
  • Comments: 42 (1 by maintainers)

Commits related to this issue

Most upvoted comments

Hey, I have the same issue. My json file is located in root, and it works fine locally, but when trying to load it on Vercel, I get the ENOENT: no such file or directory, open '/var/task/file.json error.

Using NextJS 13 app router

Hey, I have the same issue. My json file is located in root, and it works fine locally, but when trying to load it on Vercel, I get the ENOENT: no such file or directory, open '/var/task/file.json error.

Using NextJS 13 app router

I had the same problem and could fix it by moving my json file to public folder. So in my project root I have api and public folders and in my api serverless function I can read json like this:

import path from 'path';
import fs from 'fs';

const jsonPath = path.join(process.cwd(), 'public', 'data.json');
const jsonContent = fs.readFileSync(jsonPath, 'utf8');

I have the same problem and I’m not using any frameworks even. My json folder is in root and it works with vercel dev locally, but when deployed the path is logged as /var/task/json/data.json and can’t be found, though I see on Vercel’s website under source > output that the json folder and data.json file exist. In my serverless function I’m reading the file like this:

fs.readFileSync(path.join(process.cwd(), 'json/data.json'));

Same issue here.

Did anyone find a solution to this problem?

I found the answer here: https://github.com/shikijs/shiki/issues/138#issuecomment-1057471160

basically in nextjs there are 3 states:

  • build-time, on server -> this is getStaticProps
  • run-time, on server -> this is getServerSideProps, or getStaticProps in case of ISR, which is this issue
  • run-time, on client

We want Shiki on getServerSideProps. This means:

  • ALL languages are available
  • ALL themes are available
  • NONE of them are bundled into client side

The trick is:

  • Copy shiki/themes and shiki/languages to somewhere outside of node_modules, maybe under lib/shiki
  • Touch these folders in a server side function (e.g. fs.readdirSync)
  • Done!

The key here is to let Vercel nft to know about the existence of Shiki/themes and shiki/languages so they are included in the production run-time

Sample code: https://github.com/thien-do/memos.pub/blob/a3babb1f149f05c43012278331f885d81f5fcfac/lib/mdx/plugins/code.ts

credit to thien-do

I was having similar issues, and the solution I found was to add the following to my settings:

experimental: {
    outputFileTracingRoot: path.join(__dirname),
    outputFileTracingIncludes: {
      "/api/**/*": ["src/components/recipes/**/*"]
    }
  }

Maybe it’s my inexperience, but I spent a lot of time browsing the docs to find this guide. Here is my repo. I hope it helps.

const jsonPath = path.join(process.cwd(), ‘public’, ‘data.json’);

I have my file in the public folder too, and do exactly what you do here, but I still get the following error:

Error: ENOENT: no such file or directory, open '/var/task/public/images/map_western_cape_kruger.jpg'

The picture is available when browsing https://project-name.vercel.app/images/map_western_cape_kruger.jpg

Any idea? Thank you

I’m facing the same issue. Already tried these to no avail:

  1. placing my content (.md) under the public folder
  2. using path.join(process.cwd(), "public", ...) in the serverless function
  3. using generateStaticParams() for each piece of content (e.g., blogposts)

Hey guys I also had this problem, try using an api route to read your file, It is the only way that worked for me. Happy Coding! 😊

stuck here too, must be an issue with vercel. their guide literally describes doing exactly what we are doing, but it breaks with the error above https://vercel.com/guides/loading-static-file-nextjs-api-route

process.cwd() is returning /var/task/ when run on the vercel sever.

when I use this hash URL, it works.

You don’t get it. The image is accessible on the different domains as it is in the public folder (branch, preview, etc.). The problem is when trying to reading it from the server with fs.readFileSync for instance. On the frontend I get this:

image

In the logs I have: Error: ENOENT: no such file or directory, open '/var/task/public/images/map_western_cape_kruger.jpg'

Here is my code:

import path from 'path';
import getImageSize from 'image-size';
import Image, { type ImageProps } from 'next/image';
import { cn } from '@/libs/utils';

interface MdxImageProps extends React.ImgHTMLAttributes<HTMLImageElement> {}

export default function MdxImage(props: MdxImageProps) {
  if (!props.src) return;

  const newProps = { ...props };
  const isLocalImage = !props.src.startsWith('http');

  newProps.className = cn('m-auto', newProps.className);

  if (!props.width && !props.height && isLocalImage) {
    const filePath = path.join(process.cwd(), 'public', props.src);
    const dimensions = getImageSize(filePath); // <===== I guess it breaks here

    newProps.width = dimensions.width;
    newProps.height = dimensions.height;
  }

  return <Image {...(newProps as ImageProps)} alt={newProps.alt || ''} />;
}

const jsonPath = path.join(process.cwd(), ‘public’, ‘data.json’);

I have my file in the public folder too, and do exactly what you do here, but I still get the following error:

Error: ENOENT: no such file or directory, open '/var/task/public/images/map_western_cape_kruger.jpg'

The picture is available when browsing https://project-name.vercel.app/images/map_western_cape_kruger.jpg

Any idea? Thank you

This is likely related to next-mdx-remote and Shiki. Sounds like the file tracking is not handling it correctly.

still facing same issue in 2025.

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

Do we have any updates on this ? I am running in the same issue

Error: ENOENT: no such file or directory, open ‘/var/task/public/data.json’

Not too sure about the maintainability of the solution proposed by alivault #52711 (comment)

EDIT :

Hey guys I also had this problem, try using an api route to read your file, It is the only way that worked for me. Happy Coding! 😊

did this & it works fine but Next could put a disclaimer on their website if such behavior is intended at least

I solved the problem for myself this way:

const dataFilePath = path.resolve(process.cwd() + '/app/public/data.json') (Read-only)

You can’t write data to vercel, only read it, because you don’t have full access to the disk. I recommend you to read from https://github.com/vercel/vercel/discussions/5320.

As for media storage, it is better to use Vercel Blob.

I changed the domain and it worked

I don’t understand. My issue is the error on the backend when trying to load a page which has a server logic of reading the image. I don’t see the relation with the domain, as it is only backend issue here.

No fix for this issue yet? I am having the same problem in production (Vercel)

@dangminhngo you won’t see the shiki assets in the .next folder because Next.js uses webpack to bundle and optimize the application. During this process, files might be renamed, minified, and split into different chunks. This could include combining various dependencies into common chunks, so finding individual files might be challenging.

The critical aspect of the solution above is that it makes Vercel aware of the existence of the Shiki assets so they are included at runtime on the server. The exact location in the build folder might not be straightforward to identify, but as long as the deployed site is working as intended, it indicates that the assets are being correctly handled.

Did anyone find a solution to this problem?

does it occur when you navigate to a dynamic page? for example if your building a blog website it would be at www.website.com/blog/your-dynamic-blog-post

if so then you might need to use next.js 13 generateStaticParams() function if your not already doing so, as this occurred with me as well until I generated my static params and the error went away

Still no response from nextjs team😔