Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Validation prints `Not found [target]` message for every flag

Open
#680 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
cli

Research direction

Start by tracing the validation path and how positional arguments are determined for --validate, --ext, and --attr. Reproduce the command from the report, then adjust the handling so valid flag values do not produce “Not found” messages while validation and flag parsing continue to work.

Written by the indexing model from the issue text.

Description

Version used is 0.9.91.

Running validation with any flags prints a message to console due to how the positional args are determined.

E.g. running --validate src/ --ext foo --attr bar results in:

Not found: /foo
Not found: /bar

This is more of a cosmetic issue. I was confused at first when I saw the messages and unsure if my flags were even correctly parsed or not (turns out they are).

Dominant language
JavaScript
Stars
3.8k
Forks
171
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bigskysoftware/_hyperscript

All issues in bigskysoftware/_hyperscript

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.