-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[NV-2314] 🐛 Bug Report: Many warnings during webpack compile process. #3400
Comments
thank you for the report @vitto-moz! |
@scopsy can i work on this one? |
Sure @marooncoder09 Assigning this to you! |
thanks |
Can I work on this issue? |
@marooncoder09 Just checking if you are still working on this. If not assign it to me |
I'm facing the exact same issue, I got around 170 warnings due to missing files |
@pruthvirajjadhav1 are still willing to take a look at that? Let me know so I can assign you 🙏 |
@scopsy Can I try to fix the issue? |
@ankur0904 Good thanks, let me known if you need something related to this issue ;) |
@FlorianRuen Thanks. I will reproduce the error. |
@FlorianRuen I reproduced the error. I observed the main error is
|
@ankur0904 Yes I see the same error, got around 170 warnings. Two raisons : unused files the refeence need to be removed or used files and you need to find why these files are missing |
@FlorianRuen okay |
@ankur0904 Just coming back on this subject, do you have any update or still working on it ? |
@FlorianRuen Actually, I had my university exam last week so unable to make any progress on this issue. But I will try my best to fix this error and update you within 3-4 days. |
The
@FlorianRuen Any suggestion on how to fix this issue? |
@ankur0904 And what is the content of dist folder ? Because I think the src are the raw sources, and the dist are the compiled one, so maybe this is just a wrong matching or something |
I think the file
What is strange here, we got both js file and TypeScript files for same file |
@FlorianRuen Yes, you are right. |
@FlorianRuen What should we do next to fix the error? |
Any news? |
@tolgig On my side, I didn't get some time to go deeper on how to fix this issue |
I seem to be getting this error too, using "@novu/notification-center": "^0.20.0" Any updates around a fix for this? |
Hey folks, did you ever figured out what is the issue here? I can maybe take a look during my free time but I just wanted to understand if there's already some ideas on how to fix it? |
@MarcoBomfim Hey, I didn't have time to check deeper this issue, but it seems the problem is due to wrong paths for libraries (check my message #3400 (comment)) During compilation, several paths seem broken, which causes libraries not to be found, and therefore this multitude of errors |
Hey @FlorianRuen thanks. I did a quick investigation on Friday (with my limited bundling skills), but couldn't pick out what's going on. The mapping seems to be wrong as you said, but I tried several different things and still couldn't get rid of the warning. One thing caught my attention, I trired running When extracting the file (
When first unpacking it, This apparently didn't help with the warnings though. I'm just adding this here in the hope that someone who knows more about webpack might have a hunch of a fix. EDIT: Forgot to mention another curious thing, I noticed two other things:
|
fix it we're facing errors for this |
@FrontMizfaTools in the next 2 weeks we are releasing a brand new Inbox component redesigned from the ground up, much smaller bundle size, much more flexibility on styling, and performance improvements. I will post here once we have something. |
Tnx for that. I'm checking this issue everyday. because we need sourcemaps and this is a huge problem for us. |
@FrontMizfaTools please take a look at the new component: https://docs.novu.co/inbox/react/get-started We will be rolling new and updated docs with more details in the next 1-2 weeks |
I have installed @novu/react and now I'm facing this error: TypeError: (0 , _ui.NovuUI) is not a constructor |
hey @FrontMizfaTools! 👋 |
Hello.
Commented code would work If I install notification-center again. but new code with @novu/react. my default code would work fine and new one is not. and in terminal:
|
@FrontMizfaTools Thank you for providing additional details. We are looking at this. |
@FrontMizfaTools hey 👋 |
Frontend errors disappeared and rendered without error. 👍 |
@FrontMizfaTools are you using a self-hosted version of Novu? In that case we might not released the latest docker images yet |
@scopsy sorry, is this new component you mentioned above fixing the warning messages on the console? Or is this a separate topic? |
Yes it is 🙏 |
And when can we use self-hosted version? |
This has been resolved by the new Inbox component with the updated docker images 🙏 |
📜 Description
Hi, we use
"@novu/notification-center": "0.14.0"
for our web application and there are many warnings during webpack compile process.👟 Reproduction steps
"@novu/notification-center": "0.14.0"
👍 Expected behavior
There should not be warnings
👎 Actual Behavior with Screenshots
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
None
NV-2314
The text was updated successfully, but these errors were encountered: