-
Notifications
You must be signed in to change notification settings - Fork 17
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: Can't resolve '@svgr/webpack' #2
Comments
Thanks for opening this issue. When creating this library, I did not test it with the Next.js framework. The @svgr/webpack package is a dev dependency for this library and therefore is required for use. Please provide some more info about your project:
In the meantime, I found this stack overflow issue that seems similar to the one you are having. |
Same here, I'm using the latest version of NextJS, and this package doesn't works :( Import trace for requested module: |
Exactly the same issue here. I'm using NX mono repo with a React app. |
This looks to be an issue with how this library interacts directly with @svgr/webpack, which is essentially a webpack-only package. Cant work out why installing it directly in the project doesnt work though (as @JJ810 reported above) |
Did anyone manage to get this working with Next.js? I've got the same error as @lucasbara |
Running into this problem using ReactJS and Vite. I can install the package (with a required --legacy-peer-deps because I'm using react 18 with vite), but the moment I import the project fails to build.
|
same issue here with plain React + Vite... the problem is that this is a webpack focused lib so it expects a loader I'd recommend to simple download the assets folder, place it in your repo, and import directly the svgs.. https://github.com/shed3/react-crypto-icons/tree/main/lib/assets |
Hello! I am trying to use this library in my Next.js crypto project. And I am getting this error when I install this library.
P.S: I even tried to install
@svgr/webpack
library but then I get another issue.The text was updated successfully, but these errors were encountered: