Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Can't resolve 'fs/promises' #1612

Closed
its-dibo opened this issue Jun 4, 2020 · 6 comments
Closed

Can't resolve 'fs/promises' #1612

its-dibo opened this issue Jun 4, 2020 · 6 comments

Comments

@its-dibo
Copy link

its-dibo commented Jun 4, 2020

I use the latest version of nodejs, typescript and webpack.

for this code:

import * from "fs/promises"

running tsc compiles the files without any problem, but with webpack I got the error
Module not found: Error: Can't resolve 'fs/promises'

@alexander-akait
Copy link
Member

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.

Please read documentation https://webpack.js.org/configuration/node/

@alexander-akait
Copy link
Member

You feedback is not help, please provide example how we can reproduce it

@alexander-akait
Copy link
Member

If you don't have anything good to say, better don't say anything because what you just said is not help either.

Don't be toxic, we ask you to create an example problem for a reason

It was fixed in webpack v5 (promises) without as, if you provide more information I can look

@alexander-akait
Copy link
Member

@AngelHdz

I AM THE ONE BEING TOXIC!?!? Ha ha haha! Arrogant people always reflect on others and they love the word toxic only when they say it to others, but they never stop to think "wait, what If I am being toxic?"

I haven't told you a single harsh word, only ask about example of problem.

Bah. I rarely have to deal with people like you. Fortunately, there are more kind people in these places, so I will ignore you.
And thanks to other kind people (not like you), I found the solution to my issue and also contributed (I think?) to the original poster.

You have the right to do what you want.

Even more, you did not open this problem, did not provide any information, only shame me. How can I know your environment?

We ask developers to use the issue template to avoid unnecessary questions and help as quickly as possible. I apologize if I cannot help you.

@robo6633
Copy link

robo6633 commented Oct 16, 2022

If you don't have anything good to say, better don't say anything because what you just said is not help either.

Don't be toxic, we ask you to create an example problem for a reason
It was fixed in webpack v5 (promises) without as, if you provide more information I can look

I AM THE ONE BEING TOXIC!?!? Ha ha haha! Arrogant people always reflect on others and they love the word toxic only when they say it to others, but they never stop to think "wait, what If I am being toxic?"

Bah. I rarely have to deal with people like you. Fortunately, there are more kind people in these places, so I will ignore you.

And thanks to other kind people (not like you), I found the solution to my issue and also contributed (I think?) to the original poster.

Thanks for nothing! https://github.com/alexander-akait

You shouldn't stress with people like him, he's clearly "too smart" to answer your question. The proof if that instead of helping people with their issues he just closes them down without even bother.

@AMohamedAakhil
Copy link

yapper

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants