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

Line number for error trace.

Open
  • Is something wrong?
#287 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
developer-experience

Research direction

Start by locating the hyperscript error-trace path and the token representation mentioned in the issue. Check how token line numbers are retained and how syntax errors are reported. Done means syntax errors include a useful source line number in the error trace.

Written by the indexing model from the issue text.

Description

Is there any way for hyperscript's error trace to report the line number?

1cg mentioned:

I believe we keep the line number of tokens around, we should be able to do that

Would be nice, it really sucks to get hung up tracking down syntax mistakes while learning hyperscript! I usually just comment block out problematic code but we dont have a multiline comment. 👀 So it can get tedious.

Thanks!

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

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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.