Description

This PR fixes the "Invalid column number (column -1 requested)" error that occurs when using eslint-disable-line or eslint-disable-next-line comments within <style> blocks in Vue single-file components.

Problem

When processing eslint-disable comment directives within CSS, the code was setting the column value to -1 in lib/styles/context/comment-directive/index.ts. This caused an error when ESLint's getIndexFromLoc method was called with this invalid column number, as it expects non-negative column values.

The error manifests as:

Parsing error: Invalid column number (column -1 requested) vue-scoped-css/no-parsing-error

This typically appears at the <style scoped> tag line in Vue SFC files.

Solution

Changed the column value from -1 to 0 to indicate the start of the line, which is a valid column position. This change maintains the functionality of applying directives to entire lines while providing a valid column number.

Changes

1. Fix in lib/styles/context/comment-directive/index.ts: Changed const column = -1; to const column = 0;
2. Added test cases: Created comprehensive test cases to ensure eslint-disable comments don't cause parsing errors

Testing

• All existing tests pass (833 tests)
• Added new test cases specifically for this fix
• Tested with various comment directive patterns:
  • /* eslint-disable-line */
  • /* eslint-disable-next-line */
  • Rule-specific directives like /* eslint-disable-line vue-scoped-css/no-unused-selector */

Related Issues

This fixes the parsing errors that many users experience when using this plugin with Vue 3 projects, particularly visible when the vue-scoped-css/no-parsing-error rule is enabled.