🐛Vite - Internal server error: Failed to resolve import

[amankumarrr]

Describe the issue that you're seeing. Any Loom videos or screenshots usually help a lot!

I'm attempting to use aliases for imports, but I'm encountering an issue where Vite is unable to resolve the paths when generating config.prebuild.jsx.

Reproduction

https://github.com/amankumarrr/tina-module-alias-issue

Steps to reproduce

From Reproduction URL

• yarn run

Steps to Reproduce from a new Starter repo

• Add aliases in tsconfig (https://nextjs.org/docs/app/building-your-application/configuring/absolute-imports-and-module-aliases)
• Update the imports path (i.e from ../../components/blocks/hero to @/components-blocks/hero) in page.ts
• yarn run

System Info

Windows 11
Browser
- Chrome 
- Edge

Screenshot:

Figure: Error getting while importing templates using alias

Validations

• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that reports the same bug.

[AntonWeigel]

I am experiencing the same issue with my code. I use a path alias in my tsconfig.json that isn't recognized by Vite:

    "paths": {
      "@/*": ["./*"]
    }