nuxt-modules / nuxt-modules/html-validator

How to find the error file?

Open
#136 4 comments 13 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
TypeScript
Stars
201
Forks
24
Avg merge
2h 45m
Merged PRs (30d)
13

Description

Problem:

I can't find the exact problem pointed by @nuxtjs/html-validator.

Expected:

To have more detail for each error, like the filename, or at least the surrounding code.


I have a big medium-size project with dozens of pages and components.

I've just installed @nuxtjs/html-validator and run.
It has successfully found some errors:

 ERROR  HTML validation errors found for /my-url-route

inline
  591:375   error  <h1> cannot be empty, must have text content                        empty-heading
  591:649   error  Anchor link must have a text describing its purpose                 wcag/h30
  593:866   error  <input> is missing required "type" attribute                        element-required-attributes
  593:866   error  <input> element does not have a <label>                             input-missing-label

As I have only 1 <h1> tag, it was easy to find the first bug, but as I use lot's of components, in some cases, I can't know exactly where the problems are.

I feel like I'm missing something fundamental here. Am I not using the took correctly?

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.

Research direction

Reproduce the reported validation errors in a Nuxt project using @nuxtjs/html-validator, starting with the route and line/column output shown in the issue. Trace how those diagnostics are assembled and define done as reporting enough source context to identify the affected file or component; no test file is named, so add coverage alongside the relevant output path.

Written by the indexing model from the issue text.

Assessment

Tech stack
nuxt
Domain
accessibility, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.