-
-
Notifications
You must be signed in to change notification settings - Fork 536
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
require() of ES modules is not supported #1452
Comments
If this is a tsconfig-paths bug, then it should be reported on their issue tracker. Is that the case? |
I'm not sure, however |
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>
.
|
big thanks for your quick response, I already opened an issue there however, how to solve this issue from my side? |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
The text was updated successfully, but these errors were encountered: