We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.0.1
https://github.com/paulochoi/notus-pro-bug
Microsoft Windows
PC
Latest Google Chrome and MS Edge
Add a navBar component and try to run code.
Code to compile
The NPM package @notus-pro/react is looking for a JPG that does not exist within the source code.
Error is: ./node_modules/@notus-pro/react/CardBlogFullBgAuthor.js:49:0 Module not found: Can't resolve 'assets/img/sections/unsplashs.jpg'
Import trace for requested module: ./node_modules@notus-pro\react\index.js ./components\NavBar.tsx ./pages_app.tsx
https://nextjs.org/docs/messages/module-not-found
Comment out the line ./node_modules/@notus-pro/react/CardBlogFullBgAuthor.js:49:0
The text was updated successfully, but these errors were encountered:
same issue
Sorry, something went wrong.
No branches or pull requests
Version
1.0.1
Reproduction link
https://github.com/paulochoi/notus-pro-bug
Operating System
Microsoft Windows
Device
PC
Browser & Version
Latest Google Chrome and MS Edge
Steps to reproduce
Add a navBar component and try to run code.
What is expected?
Code to compile
What is actually happening?
The NPM package @notus-pro/react is looking for a JPG that does not exist within the source code.
Error is:
./node_modules/@notus-pro/react/CardBlogFullBgAuthor.js:49:0
Module not found: Can't resolve 'assets/img/sections/unsplashs.jpg'
Import trace for requested module:
./node_modules@notus-pro\react\index.js
./components\NavBar.tsx
./pages_app.tsx
https://nextjs.org/docs/messages/module-not-found
Solution
Comment out the line ./node_modules/@notus-pro/react/CardBlogFullBgAuthor.js:49:0
Additional comments
The text was updated successfully, but these errors were encountered: