Extracting meteor-tool@3.5.1... has been running for >1h
- Dominant language
- JavaScript
- Stars
- 44.8k
- Forks
- 5.2k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 25
Description
Hello,
I am on Windows 11 and extraction of `meteor-tool@3.5.1` files as part of the update has been running for >1 hour. How do I accelerate this?
- Meteor is already installed.
- 3.5.1 was released and any `meteor` command issued outside of a project bound to a specific meteor version will trigger the update. I don't have any information on what is being extracted and from where or an indication of progress.
I did the same on WSL on the same PC, it took a couple of minutes max. I disabled virus scanning, no difference.
I checked relevant issues https://github.com/meteor/meteor/issues/9592 - no solution was provided there.
Edit: It is not only the installation of meteor that is slow on Windows 11, `meteor run` operations also take >20min, the same operation on a Linux PC with comparable hardware takes <1min. I am not sure if this is a symptom of the same underlying issue as for the reported issue.
Thank you,
David
Contributor guide
Research direction
Reproduce the meteor-tool@3.5.1 extraction and meteor run timings on Windows 11, then trace the meteor-tool update and meteor run entry points. Compare the behavior with WSL or Linux and review issue #9592 for prior investigation. Done means identifying the cause of the Windows-specific slowdown and verifying a fix against both operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100