Issue:
The checkNewVersion function is using await, which blocks the dev and build commands. As a result, both commands are delayed until checkNewVersion finishes executing. This adds unnecessary wait time before starting these processes.
Proposed Solution:
Consider making checkNewVersion non-blocking. One possible approach is to trigger checkNewVersion asynchronously without await, allowing the dev and build commands to run in parallel. The version check could happen in the background and optionally log results when finished, without affecting the command startup time.
If you still want to notify the user about a new version, logging could happen after the command starts, without delaying the process execution.
Version
Latest
What OS are you seeing the problem on?
No response
What browsers are you seeing the problem on?
No response
Relevant log output
No response
(OPTIONAL) Contribution
[X] I would like to fix this BUG via a PR
Code of Conduct
[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.
What happened?
Issue: The checkNewVersion function is using await, which blocks the dev and build commands. As a result, both commands are delayed until checkNewVersion finishes executing. This adds unnecessary wait time before starting these processes.
Proposed Solution: Consider making checkNewVersion non-blocking. One possible approach is to trigger checkNewVersion asynchronously without await, allowing the dev and build commands to run in parallel. The version check could happen in the background and optionally log results when finished, without affecting the command startup time.
If you still want to notify the user about a new version, logging could happen after the command starts, without delaying the process execution.
Version
Latest
What OS are you seeing the problem on?
No response
What browsers are you seeing the problem on?
No response
Relevant log output
No response
(OPTIONAL) Contribution
Code of Conduct