Replies: 2 comments
-
So apparently running
If I switch My questions would be:
|
Beta Was this translation helpful? Give feedback.
-
My response times were even worse, over 2 seconds on a Macbook Pro 2019. The app is very small so I'm not sure what's going on. Thank you for the workaround, it significantly speeds up the build! This should be addressed, the dev experience of the Blues stack https://github.com/remix-run/blues-stack became very frustrating after a good week of developing in it, to the point I was going to give up and switch frameworks until I found this thread. |
Beta Was this translation helpful? Give feedback.
-
Hi 👋
I've been off for a week. This morning, I ran my project in dev mode (
npm run dev
) and saw massive response times: 1500ms at best..I've made close to no (big) changes today, so I'm not sure what happened. Strangely enough, I've pushed the project as it is to fly and the response times are (seem?) as usual: lightning fast ⚡.
My laptop was running the project fine one week ago, and current CPU usage is normal. I have no clue what is going on.
I digged in my git log and located the difference between two commits.
On my commit 470c48d:
On the following commit f8235e6:
If I perform a
git diff
between the two commits, I noticed I've installed three new libraries:How can I profile if one of this library is the cause? I tried to use the DevTools for Node.js Profiler from Chrome, but I'm unable to interpret the content, although it is clear way much more is happening:
For the commit 470c48d:
For the commit f8235e6:
Noticed the
transpileModule
thing happenng? Could it be that a module needs heavy work in dev mode?Any help would be greatly appreciated 🙏 🙏
Beta Was this translation helpful? Give feedback.
All reactions