tsconfig paths do not work in vite.config.ts

[Enteleform]

Describe the bug

paths added to tsconfig.node.json are not able to be imported when running vite.

Expected:
Aliased paths will be imported successfully.

Actual:
ERR_MODULE_NOT_FOUND is thrown.

Reproduction

enteleform-codesandbox/0016--Vite--TypeScript-Paths@c970d37

System Info

System:
    OS: Windows 10 10.0.19044
    CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz    
    Memory: 34.67 GB / 63.96 GB
  Binaries:
    Node: 18.8.0 - C:\_\Dev\NodeJS\18\node.EXE
    Yarn: 1.22.19 - C:\_\Dev\NodeJS\18\yarn.CMD
    npm: 8.18.0 - C:\_\Dev\NodeJS\18\npm.CMD
  Browsers:
    Chrome: 105.0.5195.102
    Edge: Spartan (44.19041.1266.0), Chromium (105.0.1343.27)
    Internet Explorer: 11.0.19041.1566

Used Package Manager

npm

Logs

Click to expand!

> vite

failed to load config from D:\0016--Vite--TypeScript-Paths\vite.config.ts
error when starting dev server:
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'VitePlugins' imported from D:\0016--Vite--TypeScript-Paths\vite.config.ts.timestamp-1662805287895.mjs
    at new NodeError (node:internal/errors:393:5)
    at packageResolve (node:internal/modules/esm/resolve:810:9)
    at moduleResolve (node:internal/modules/esm/resolve:859:20)
    at defaultResolve (node:internal/modules/esm/resolve:1074:11)
    at nextResolve (node:internal/modules/esm/loader:164:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:839:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:426:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:40)
    at link (node:internal/modules/esm/module_job:75:36)

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

I don't think this is a bug.
I agree with this explaination here from ts-node's README. (Vite doesn't use ts-node though.)

related: #6828

[bluwy]

I think this should be closed in favour of #6828. It would be confusing if the tsconfig paths work in vite.config.js but not in the Vite project. We should have it both working for this feature.