-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Module not found: Error: Can't resolve 'p-queue' after updating to 7.1.0 #145
Comments
This is not the place to ask for support regarding Webpack or webpack-dev-server. This package works fine with plain Node.js. I would open an issue on Webpack or webpack-dev-server asking for help there. |
I have the same problem with parcel on version 7.1.0, but it works fine with version 6.6.2. |
I also have the same problem with 7.1.0 with webpack build. I'm downgrading to 6.6.2. |
I had the same issue with an Thanks for the tip! Downgrading to 6.6.2 solved it for me. |
@sindresorhus this is an issue with this lib. |
Ran into the same issue. Importing |
I'm having the same problem in here and I think this isn't a problem with this library. I think, however, for compatibility reasons, a "module" field is missing on this lib's package.json so tools like tsdx (that uses rollup) can work fine. |
The error maybe package not export main entry point I'm try local, add the |
Fixes the issue: sindresorhus#145 A similar issue and fix can be found from instance here: uuidjs/uuid#449
Ref sindresorhus/p-queue#145 (comment) Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
It indeed runs just fine with plain javascript. Another issue is that it confuses eslint-plugin-import on This isn't the case with |
Doing some research, it seems that Line 9 in c12ec2e
Meanwhile the other packages don't have a build step but instead
I'm guessing that webpack and other bundlers, when they don't find a |
This should be documented somehow 🤔 |
After wasting hours of my life looking for a solution to this, the only thing that comes to my mind is:
I love TS, but it's impressive how you just waste a ton of time chasing around zero-value env-related issues because someone decided that ESM was a good idea. Sorry for the rant Back to work |
Ok it works, you just need to redeclare the types
|
6.6.2 => 7.1.0
I've found a pretty similar issue title before, but that one was related to react-scripts start command
It works with the previous Major version. I moved to ESM (replaced requied() to import). Any ideas?
node version 14.x
p-queue 7.1.0
using webpack-dev-server (^3.11.1)
The text was updated successfully, but these errors were encountered: