Closed omerson-cruz closed 1 year ago
omerson-cruz
commented
1 year ago Just a correction with my issue report. Console Ninja actually works on V0.0.45 and below. Although I'll be missing some of the features though if I do use the older versions
ArtemGovorov
commented
1 year ago Can you please
omerson-cruz
commented
1 year ago Hi @ArtemGovorov, I've tried the first step you suggested.
try closing all VS Code instances, stopping all running dev servers, checking if there are any node processes still running after it in your system and killing them (or restarting your machine), then re-open the project in VS Code and check if the issue is still there?
And also just to add an information to the issue. I am seeing this error log on the Console Ninja output window instead of showing the actual console.log()
And if I try to click that error this is what the link to the file contains.
I'm not sure if this information would help but yeah I'm trying to prepare a somewhat similar sample project to our dev environment that I can share.
omerson-cruz
commented
1 year ago @ArtemGovorov: I added you on the private repo https://github.com/omerson-cruz/sample-webpack-for-cn/invitations
ArtemGovorov
commented
1 year ago Thanks, I have tried starting the project, but after running npm run start in my dev container for 20 minutes webpack is either hanging forever or is still bundling (with and without console ninja started), but the app doesn't start.
To try run the app in some capacity, I have edited src/index.js and src/App.js to have a simplified app, while still starting it with the existing webpack config and infra that you have configured in the project, and it's working for me as expected:
So the issue may be related to some other specific source files or transforms that webpack maybe doing, but unfortunately I can't get to that point as it is hanging for me.
Can you please try doing what I have done (simplifying index.js and App.js and addign a simple logging) to check if it's working for you? If so, can you please try adding minimal (otherwise there's a risk that I won't be able to run it in our test environment) number of other dependencies/imports to reproduce the issue?
omerson-cruz
commented
1 year ago Hi @ArtemGovorov , thanks for the fast response. I've tried what you said like simplifying or adding minimal code to the App.js component. and it works for me similar to your SS.
Although with the real project that I'm working on, The console log is really deep within the application's components I'll just try to replicate the same scenario as much as I can and yes reduced some of the dependencies or imports so it wont hang on your end during testing.
Oh and one thing is that with the latest Console Ninja I think the webpack dev server becomes very slow and you're right it hangs for some reason and it's making my WSL to eat lot of RAM for some reason.
But again using the old Console Ninja version I was not able to encounter such issue which is weird.
omerson-cruz
commented
1 year ago Just an update on this issue. I managed to make it work with the latest version. Though not sure what exactly fix the issues since it's really hard to replicate on a controlled setup. But here's what I did.
Then it works :).
I think we can close this ticket thanks
What happened?
The logs only started showing after I killed the local react Dev server. I think it only happens on the latest versions. Cause I tried using older versions like v.0.0.50 and it works.
After attempts of restarting my local dev server and restarting Console Ninja, Issue is still there.
https://user-images.githubusercontent.com/65213312/224826555-add8f1b4-7968-4700-831c-8e738b2c6a64.mp4
Version
V.0.0.84
Steps to reproduce (or sample repo)
Run local dev server(webpack)
Log output