skills.rest
markuplint
markuplintOFFICIAL
Explore all skills by this author →
Website𝕏@markuplintGitHub

migrate4-5

Migrates markuplint configuration and dependencies from v4 to v5.

611|63|Updated Sep 26, 2017
Search Tags:#upgrade#Configuration#markuplint#Migration#Breaking Changes#html linter#v4 to v5
One-click install
npx skills add https://github.com/markuplint/markuplint --skill migrate4-5
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate4-5
Source: https://github.com/markuplint/markuplint/tree/main/skills/migrations/v4-v5
Command: npx skills add https://github.com/markuplint/markuplint --skill migrate4-5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading markuplint from v4 to v5 involves renamed and split rules, changed preset contents, new severity defaults, and silent coverage gaps that produce no deprecation warnings, making manual migration error-prone.

Core Features & Use Cases

  • Guided Migration Workflow: Detects installed markuplint versions, locates config files, verifies Node.js v24+, and walks through the official v4-to-v5 migration guide.
  • Interactive Breaking-Change Review: Confirms each applicable breaking change with the user, including rule renames, preset additions, ARIA 1.3 defaults, and CI warning behavior.
  • Config and Test Updates: Rewrites deprecated rule names, updates package versions, converts framework parser/spec entries, and adjusts test assertions for v5 behavior.
  • Use Case: A team running markuplint v4 in CI wants to upgrade to v5 without losing lint coverage; the skill identifies silent gaps like raw permitted-contents usage and adds the sibling rules needed to preserve v4 behavior.

Quick Start

Ask the assistant to migrate markuplint from v4 to v5 in this repository and confirm each breaking change interactively.

Frequently Asked Questions about migrate4-5

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate markuplint from v4 to v5?▼

Run the guided migration which detects your installed markuplint versions, reviews the official v4-to-v5 migration guide, confirms each breaking change with you, then updates dependencies, config files, and tests. Node.js v24.0.0 or later is required before upgrading packages.

What breaking changes does markuplint v5 introduce?▼

v5 renames and splits rules such as required-element to require-element and invalid-attr into three rules, changes preset contents for recommended and a11y, defaults ARIA to 1.3, escalates table-model rules to errors, and makes --config stop merging auto-discovered config files.

Does markuplint v5 work with htmx or Alpine.js?▼

Yes, but the packages changed. For htmx, replace @markuplint/htmx-parser with @markuplint/htmx-spec and drop the parser entry. For Alpine, keep the parser but switch the spec from @markuplint/alpine-parser/spec to @markuplint/alpine-spec.

Why does markuplint v5 report new errors without config changes?▼

v5 tightened built-in spec-conformance checks, so markup that passed under v4 can now fail. Examples include stricter URL validation, IANA subtag checks on lang attributes, MathML child-count enforcement, and ARIA restrictions on presentational elements.

What Node.js version does markuplint v5 require?▼

markuplint v5 requires Node.js v24.0.0 or later, up from the v18.18.0 documented for v4. Upgrade Node before changing any markuplint packages, otherwise the migration should stop.

Related Skills

Explore More Software Engineering Skills→
naporin0624naporin0624
3

html-lint-runner

Run axe-core/playwright and markuplint checks on HTML, JSX, and TSX files.

Community
Intermediate
GoogleCloudPlatformGoogleCloudPlatform
1.1k

update-client-library-version

Updates Google Cloud Go client libraries across Config Connector modules and validates fuzz tests.

Official
Intermediate
tyler-dot-earthtyler-dot-earth
1

tanstack-query

Provides comprehensive guidance for TanStack Query v5 in React apps.

Community
Advanced
FlukeSupakornFlukeSupakorn
1

migrating-tauri-apps

Migrate Tauri applications from v1 or v2 beta to v2 stable.

Community
Advanced