Open thefuckingcode opened 3 years ago
The info part is us fetching plugins that you've used, npm should create a local cache so subsequent runs should be faster, if they aren't then either the plugin that you depend on updates very regularly, or it is some connection issue with npm.
The info part is us fetching plugins that you've used, npm should create a local cache so subsequent runs should be faster, if they aren't then either the plugin that you depend on updates very regularly, or it is some connection issue with npm.
Yes,i find there is some connection issue. Is there any place I can get a full list of plugins from? I want to download them all to my disk.Then modify the file 'index.js', directly using local cache.
If you open the .side
file you can see the list of plugins there, just create a package.json
with them and install them, it should create the cache.
If you open the
.side
file you can see the list of plugins there, just create apackage.json
with them and install them, it should create the cache.
ok.thanks a lot
🐛 Bug Report
Use selenium-side-runner to execute side. You will find that most of the time is spent in the info part, as shown in the picture
To Reproduce
It's very easy.Just to run the test.side.Here is my command:
selenium-side-runner --output-directory=/Users/lihao/ui-test/0-100/ --output-format=jest -c "goog:chromeOptions.args=[--headless,--nogpu,--user-data-dir=/Users/lihao/selenium] browserName=chrome" test.side
Expected behavior
less time spend on step one(which is 'info' step)
Project file reproducing this issue (highly encouraged)
All of side files have this problem on my macOs or in Docker containers
Environment
OS: OSX Selenium IDE Version: 3.17.0 Selenium SIDE Runner Version: 3.17.0 Node version: v14.4.0 Browser: ChromeDriver 86.0.4240.22