Replies: 4 comments
|
If this is a tsconfig-paths bug, then it should be reported on their issue tracker. Is that the case? |
0 replies
|
I'm not sure, however |
0 replies
|
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>
.
|
0 replies
|
big thanks for your quick response, I already opened an issue there however, how to solve this issue from my side? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have an issue when I try to run webpack with
webpack.config.tswritten in typescript andts-nodehas"require": ["tsconfig-paths/register"]// tsconfig.json
when I remove
"require": ["tsconfig-paths/register"]fromts-nodeit runs, but webpack cannot detect aliases.I already set
module: commonjsin mytsconfig.jsonand removedtype: modulefrom mypackage.jsontrace
All reactions