Replies: 3 comments 19 replies
-
Does using |
Beta Was this translation helpful? Give feedback.
-
Hey! I'm jumping in here because I'm experiencing the same issue. For my extension, v0.18 will give me the "Opened browser" message in under 2s or so. After upgrading wxt to v0.19.4 will take longer than 6s, usually closer to 8s before the "Opened browser" message appears. I tried adding I'm really not sure what could be causing the issue. Maybe some dependency I have, or just the size or complexity of my project? I noticed that there was some slowdown after upgrading some of the examples to V0.19 and downgrading github-better-line-counts to v0.18 resulted in some speed up. Nothing as dramatic as what I'm seeing, to be sure. Let me know if there's anything I can do to help track this down! |
Beta Was this translation helpful? Give feedback.
-
On my machine, I was doing some testing and found that even with firefox, occur the second launch faster issue. In addition, launching pure chrome with chrome-launcher without WXT was almost the same as the wxt@0.19.6 launch speed. And also had the second launch faster issue. If everyone else is the same, then this second faster problem might be a macOS issue. I also found the interesting thread. (https://www.reddit.com/r/MacOS/comments/1bp7ugd/why_does_it_take_so_long_to_open_apps_for_the/) |
Beta Was this translation helpful? Give feedback.
-
I upgraded from 0.18.15 to 0.19.0, and I obviously felt that the compilation speed in the development environment became very slow. Does anyone have similar experience?
Beta Was this translation helpful? Give feedback.
All reactions