Importing aliased module

[ashalfarhan]

I have an issue where I can't import my module with typescript aliases in a Next.js typescript project.

// contentlayer.config.ts
import type * as H from 'hast';
import {
  makeSource,
  defineDocumentType,
  ComputedFields,
} from 'contentlayer/source-files';
import readingTime from 'reading-time';
import rehypeAutoHeadings from 'rehype-autolink-headings';
import rehypeSlug from 'rehype-slug';
import remarkGfm from 'remark-gfm';
import rehypeShiki from '@re-taro/rehype-shiki';
import { getHighlighter } from 'shiki';
import { getImgProps } from '@site/helpers'; // Here's the module

// tsconfig.json
{
  "compilerOptions": {
     // ...other of the config
    "paths": {
      "@site/*": ["./src/*"],
      "@content": ["./.contentlayer/generated"]
    }
  },
  "include": [
    "next-env.d.ts",
    "**/*.ts",
    "**/*.tsx",
    ".contentlayer/generated"
  ],
  "exclude": ["node_modules"]
}

contentlayer version: "^0.2.5"
next-contentlayer version: "^0.2.5"

When running

yarn contentlayer build

Here's what I got

Is that possible to use path aliases with typescript to solve this?

Thanks in advance!

[schickling]

Thanks for opening this issue. Closing as duplicate of #238.