tsconfig.json support?

Hi there!

Thanks for the helpful plugin! I’m trying to integrate esbuild into rollup using your plugin and it seems that it doesn’t support tsconfig.json completely? At least it doesn’t respect compilerOptions.baseUrl and compilerOptions.paths. These are path aliases which allow to write

import '@alias/module'

instead of

import `../../../../../../../../some-folder/module`

(well, I think you know, but just for clarity 😃 ) And as far as I know esbuild itself supports these options (https://github.com/evanw/esbuild/issues/60 and https://github.com/evanw/esbuild/issues/38#issuecomment-639784830).

Or maybe I missed something?

[ycnmhd]

found a workaround using @rollup/plugin-alias

import path from "path";
import resolve from "rollup-plugin-node-resolve";
import esbuild from "rollup-plugin-esbuild";
import alias from "@rollup/plugin-alias";

const projectRootDir = path.resolve(__dirname);

export default {
  /**/
  plugins: [
    alias({
      customResolver: resolve({ extensions: [".tsx", ".ts"] }),
      entries: Object.entries({
        "::helpers/*": ["./src/helpers/*"],
        "::hooks/*": ["./src/hooks/*"]
        /**/
      }).map(([alias, value]) => ({
        find: new RegExp(`${alias.replace("/*", "")}`),
        replacement: path.resolve(
          projectRootDir,
          `${value[0].replace("/*", "")}`
        )
      }))
    }),
    esbuild({
      /**/
    })
  ]
};

[egoist]

The solution is to use @rollup/plugin-alias as @ycnmhd said, there’s also alias-hq (by @davestewart) to reduce boilerplate code.