Replies: 4 comments
-
If this is a tsconfig-paths bug, then it should be reported on their issue tracker. Is that the case? |
Beta Was this translation helpful? Give feedback.
-
I'm not sure, however |
Beta Was this translation helpful? Give feedback.
-
Tsconfig-paths does not support esm and we do, so the limitation is with
them. This has been discussed recently in other issues, so if you search
around you'll find it.
…On Sun, Sep 12, 2021, 2:54 AM Dibo ***@***.***> wrote:
I'm not sure, however tsconfig-path complains about using ES modules
which be handled by ts-node not by them.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1452 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC35OBKS4YGMSWKHHK7NE3UBRFD5ANCNFSM5D2XPUYQ>
.
|
Beta Was this translation helpful? Give feedback.
-
big thanks for your quick response, I already opened an issue there however, how to solve this issue from my side? |
Beta Was this translation helpful? Give feedback.
-
I have an issue when I try to run webpack with
webpack.config.ts
written in typescript andts-node
has"require": ["tsconfig-paths/register"]
// tsconfig.json
when I remove
"require": ["tsconfig-paths/register"]
fromts-node
it runs, but webpack cannot detect aliases.I already set
module: commonjs
in mytsconfig.json
and removedtype: module
from mypackage.json
trace
Beta Was this translation helpful? Give feedback.
All reactions