MarketSquare / MarketSquare/robotframework-browser
If installing node dependecies fails, it is sometimes problematic to find out what causes a error
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 655
- Forks
- 147
- Avg merge
- 5h 27m
- Merged PRs (30d)
- 59
Description
**Is your feature request related to a problem? Please describe.**
When installing node dependecies, it is sometimes problematic to debug installes errors
- [ ] Add possible to run with verbose flag, this will run `npx playwright install` without `--quiet` flag
- [ ] Printing tree of `wrapper/` folder is not sensible. Instead print files and folders from root of the folder. Also log folders only from `wrapper/node_modules/`
- [ ] Think could some info go only to log file and not to be show on console.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Trace the dependency-install path that invokes `npx playwright install` and handles `wrapper/` output; compare quiet versus verbose behavior and define done as actionable console or log diagnostics for each listed case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, playwright, python
- Domain
- cli, testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100