@entro314labs/markdownfix 0.0.6 → 0.0.10

package/.remarkignore

@@ -56,4 +56,6 @@ coverage/
 # Specific files to ignore
 CHANGELOG.md
 LICENSE
-README.md
+README.md
+PUBLISHING.md
+ESLINT_INTEGRATION.md

package/.remarkrc.js

@@ -1,6 +1,6 @@
 /**
  * Opinionated Remark configuration for markdown processing
- * Supports .md, and .mdx files with consistent formatting
+ * Supports .md, .mdx, and .mdc files with consistent formatting
  * Optionally supports .mdd files if mdd package is installed
  */
 
@@ -18,7 +18,7 @@ try {
   ];
   console.log('✓ MDD support enabled');
 } catch (e) {
-  // MDD package not installed - only support .md and .mdx
+  // MDD package not installed - only support .md, .mdx, and .mdc
   mddPlugins = ['remark-mdx'];
   console.log('ℹ MDD support not available (install mdd package for .mdd file support)');
 }
@@ -50,6 +50,9 @@ export default {
     // Enable GitHub Flavored Markdown (tables, strikethrough, etc.)
     'remark-gfm',
 
+    // Enable MDC syntax (Markdown Components for Nuxt Content)
+    'remark-mdc',
+
     // MDX/MDD plugins (loaded dynamically above)
     ...mddPlugins,
 

package/ESLINT_INTEGRATION.md

@@ -0,0 +1,345 @@
+# ESLint + MDX Integration Guide
+
+This project integrates `eslint-plugin-mdx` with the existing remark-lint setup to provide comprehensive linting for MDX files.
+
+## Why ESLint for MDX?
+
+While remark-lint handles markdown syntax and formatting, ESLint adds:
+
+- **JavaScript/JSX linting** - Lint code inside MDX code blocks
+- **IDE integration** - Better VS Code support with ESLint extension
+- **Unified error reporting** - Consistent error format across tools
+- **Code quality checks** - Catch unused variables, syntax errors in examples
+
+## Architecture
+
+```
+┌─────────────────────────────────────────────────┐
+│           Your MDX/Markdown Files               │
+└─────────────────────────────────────────────────┘
+                    │
+        ┌───────────┴───────────┐
+        │                       │
+        ▼                       ▼
+┌──────────────┐      ┌──────────────────┐
+│  remark-cli  │      │  eslint-plugin-  │
+│              │      │      mdx         │
+│ • Formatting │      │                  │
+│ • MD syntax  │      │ • JS/JSX linting │
+│ • 40+ rules  │      │ • Reads .remarkrc│
+└──────────────┘      │ • Code blocks    │
+                      └──────────────────┘
+```
+
+## How It Works
+
+1. **remark-cli** - Primary formatter and markdown linter
+   - Uses [.remarkrc.js](./.remarkrc.js) configuration
+   - Handles all markdown syntax and formatting
+   - Fixes issues automatically with `--output`
+
+2. **eslint-plugin-mdx** - Complementary JavaScript linter
+   - Reads [eslint.config.js](./eslint.config.js) (ESLint 9 flat config)
+   - **Automatically uses remark-lint rules** from `.remarkrc.js`
+   - Lints JavaScript/JSX code in MDX code blocks
+   - Provides IDE integration
+
+## Installation
+
+Already installed in this project:
+
+```bash
+pnpm add -D eslint eslint-plugin-mdx eslint-plugin-react
+```
+
+## Configuration Files
+
+### [eslint.config.js](./eslint.config.js)
+
+ESLint 9 flat config that:
+
+- Configures MDX plugin for `.md`, `.mdx`, `.mdd` files
+- Uses `mdx/remark` rule to integrate remark-lint
+- Enables code block linting
+- Defines globals for documentation examples
+
+### [.remarkrc.js](./.remarkrc.js)
+
+Existing remark configuration with 40+ lint rules. This is **automatically used** by ESLint via the `mdx/remark` rule.
+
+## Available Scripts
+
+```bash
+# Markdown formatting (remark-cli)
+pnpm run format              # Auto-fix markdown formatting
+pnpm run format:check        # Check without writing changes
+
+# Linting
+pnpm run lint                # Remark-lint only
+pnpm run lint:eslint         # ESLint + MDX only
+pnpm run lint:eslint:fix     # ESLint auto-fix
+pnpm run lint:all            # Both remark and ESLint
+
+# Complete workflow
+pnpm run process             # Format + lint all
+pnpm run process:safe        # Check + lint all
+pnpm run nuclear             # 🚀 Run ALL linters and fixers
+pnpm test                    # Same as process:safe
+
+# CLI usage
+markdownfix nuclear          # Nuclear mode via CLI
+mdfix nuclear --quiet        # Silent nuclear mode
+```
+
+## Workflow
+
+### Recommended Development Workflow
+
+#### Quick Fix Everything (Recommended)
+
+```bash
+# 🚀 One command to rule them all
+markdownfix nuclear
+```
+
+This runs the complete 4-step workflow:
+
+1. Remark formatting
+2. Remark linting
+3. ESLint auto-fix
+4. ESLint linting
+
+#### Manual Step-by-Step
+
+1. **Write/edit markdown files**
+
+2. **Format with remark**
+   ```bash
+   pnpm run format
+   ```
+
+3. **Lint with both tools**
+   ```bash
+   pnpm run lint:all
+   ```
+
+4. **Or use the complete workflow**
+   ```bash
+   pnpm run process
+   ```
+
+### CI/CD Workflow
+
+```bash
+pnpm test
+```
+
+This runs `process:safe` which:
+1. Checks formatting (no writes)
+2. Runs remark-lint
+3. Runs ESLint
+
+## What Gets Checked
+
+### Remark-lint (40+ rules)
+
+- Markdown syntax (headings, lists, tables)
+- Formatting consistency (emphasis, strong, code blocks)
+- Link validation
+- Table alignment
+- Line length
+- Trailing spaces
+- Final newlines
+
+See [.remarkrc.js](./.remarkrc.js) for full configuration.
+
+### ESLint (JavaScript in code blocks)
+
+- `no-var` - Enforce const/let
+- `prefer-const` - Use const when possible
+- `no-unused-vars` - Warn about unused variables
+- Syntax errors in code examples
+
+## IDE Integration
+
+### VS Code
+
+1. **Install ESLint extension**
+   ```
+   ext install dbaeumer.vscode-eslint
+   ```
+
+2. **Configure workspace settings** (`.vscode/settings.json`)
+   ```json
+   {
+     "eslint.validate": [
+       "javascript",
+       "typescript",
+       "markdown",
+       "mdx"
+     ],
+     "eslint.probe": [
+       "javascript",
+       "typescript",
+       "markdown",
+       "mdx"
+     ]
+   }
+   ```
+
+3. **MDX files will show inline errors** from both remark-lint and ESLint
+
+## Examples
+
+### Catching Code Block Issues
+
+**Before:**
+```javascript
+function example() {
+  var unused = "bad";
+  return "hello"
+}
+```
+
+**ESLint warnings:**
+- `no-var`: Unexpected var, use let or const instead
+- `no-unused-vars`: 'unused' is assigned but never used
+
+**After:**
+```javascript
+function greet(name) {
+  return `Hello ${name}`;
+}
+
+console.log(greet("World"));
+```
+
+### Markdown Issues (remark-lint)
+
+**Before:**
+```markdown
+#No Space After Hash
+- item 1
+- item 2
+  - nested
+```
+
+**Remark-lint errors:**
+- Headings must have space after `#`
+- List items need blank lines between them
+
+**After:**
+```markdown
+# Proper Heading
+
+- item 1
+
+- item 2
+  - nested
+```
+
+## Ignoring Files
+
+Files are ignored via:
+
+1. **ESLint** - `ignores` array in [eslint.config.js](./eslint.config.js)
+2. **Remark** - [.remarkignore](./.remarkignore)
+
+Common ignored files:
+- `README.md`
+- `CHANGELOG.md`
+- `LICENSE`
+- `node_modules/`
+- Build outputs
+
+## Troubleshooting
+
+### ESLint not finding MDX files
+
+Make sure you're using the correct extension flag:
+
+```bash
+# Correct
+eslint --ext .md,.mdx,.mdd .
+
+# Wrong (won't work)
+eslint .
+```
+
+### Remark-lint rules not appearing in ESLint
+
+The `mdx/remark` rule automatically reads `.remarkrc.js`. If changes don't appear:
+
+1. Restart your IDE/ESLint server
+2. Check `.remarkrc.js` syntax is valid
+3. Verify `mdx/remark` rule is enabled in `eslint.config.js`
+
+### Code block linting not working
+
+Ensure code blocks have language identifiers:
+
+```javascript
+// This will be linted
+const x = 1;
+```
+
+### Performance
+
+For large projects, you can:
+
+1. **Disable code block linting**
+   ```javascript
+   // In eslint.config.js
+   processor: mdxPlugin.createRemarkProcessor({
+     lintCodeBlocks: false
+   })
+   ```
+
+2. **Run tools separately**
+   ```bash
+   pnpm run lint        # Just remark
+   pnpm run lint:eslint # Just ESLint
+   ```
+
+## Comparison with Alternatives
+
+### Why not just remark-cli?
+
+Remark-cli is excellent for markdown formatting but doesn't lint JavaScript code in code blocks.
+
+### Why not just ESLint?
+
+ESLint alone doesn't understand markdown-specific rules like table formatting, heading hierarchy, etc.
+
+### Why not Biome?
+
+As of 2025, Biome does not support MDX or stable Markdown linting. Markdown support is on their roadmap but not yet available.
+
+### Why not Prettier?
+
+Prettier formats but doesn't lint. This project uses remark for both formatting and linting with 40+ opinionated rules.
+
+## Benefits of This Setup
+
+✅ **Comprehensive** - Both markdown and JavaScript linting
+✅ **IDE integration** - Real-time feedback in VS Code
+✅ **Automatic fixes** - Most issues can be auto-fixed
+✅ **Unified workflow** - Single `pnpm test` command
+✅ **Flexible** - Can use tools separately or together
+✅ **No conflicts** - ESLint uses remark rules, no duplication
+
+## Migration Notes
+
+If you were using only remark-cli before:
+
+1. ✅ All existing remark rules still work
+2. ✅ All existing scripts still work
+3. ✅ New ESLint scripts are additive
+4. ✅ No breaking changes to workflow
+
+## Further Reading
+
+- [eslint-plugin-mdx documentation](https://github.com/mdx-js/eslint-mdx)
+- [remark-lint rules](https://github.com/remarkjs/remark-lint)
+- [ESLint flat config](https://eslint.org/docs/latest/use/configure/)
+- [MDX documentation](https://mdxjs.com/)

package/README.md

@@ -1,6 +1,6 @@
 # Markdown Formatter (markdownfix)
 
-**Opinionated markdown formatter and linter for `.md`, `.mdd`, and `.mdx` files**
+**Opinionated markdown formatter and linter for `.md`, `.mdx`, `.mdc`, and `.mdd` files**
 
 Built on the Remark ecosystem with strict, consistent formatting rules for developer documentation, technical writing, and web content. Perfect for README files, technical docs, blogs, and GitHub wikis.
 
@@ -8,10 +8,13 @@ Built on the Remark ecosystem with strict, consistent formatting rules for devel
 
 - ✅ **Opinionated formatting** - Consistent style across all markdown files
 - ✅ **GitHub Flavored Markdown** - Tables, task lists, strikethrough, autolinks
-- ✅ **MDX support** - JSX components in markdown
-- ✅ **Comprehensive linting** - 40+ lint rules for quality and consistency
+- ✅ **MDX support** - JSX components in markdown with ESLint integration
+- ✅ **MDC syntax support** - Markdown Components for Nuxt Content
+- ✅ **Comprehensive linting** - 40+ remark-lint rules for quality and consistency
+- ✅ **Code block linting** - ESLint integration for JavaScript/JSX in code blocks
 - ✅ **Link validation** - Check for broken links
 - ✅ **Auto-fixing** - Automatically fix formatting issues
+- ✅ **IDE integration** - Works with VS Code ESLint extension
 
 ## Installation
 
@@ -35,6 +38,9 @@ markdownfix check
 # Lint files for issues
 markdownfix lint
 
+# 🚀 Nuclear mode - run ALL linters and fixers
+markdownfix nuclear
+
 # Format specific files
 markdownfix format README.md docs/*.md
 
@@ -53,7 +59,8 @@ Add to your `package.json`:
 {
   "scripts": {
     "format:md": "markdownfix format",
-    "lint:md": "markdownfix lint"
+    "lint:md": "markdownfix lint",
+    "fix:md": "markdownfix nuclear"
   }
 }
 ```
@@ -71,22 +78,27 @@ markdownfix setup
 ## What Gets Formatted
 
 ### Lists
+
 - **Unordered**: `-` (never `*` or `+`)
 - **Ordered**: `1.` incremental (never `1)`)
 
 ### Emphasis
+
 - **Italic**: `_text_` (underscore, not asterisk)
 - **Bold**: `**text**` (double asterisk, not underscore)
 
 ### Headings
+
 - **Style**: ATX (`# Title`), never setext (`===`)
 - **Hierarchy**: Must progress sequentially (no skipping levels)
 
 ### Code Blocks
+
 - Always fenced (` ``` `) with language identifiers
 - Never indented code blocks
 
 ### Formatting
+
 - **Line length**: 100 characters max with smart wrapping
 - **Tables**: Padded cells with aligned pipes (auto-formatted)
 - **Final newline**: All files must end with `\n`
@@ -94,11 +106,46 @@ markdownfix setup
 
 ## File Support
 
-| Extension | Support | Features | Use Case |
-|-----------|---------|----------|----------|
-| `.md` | ✅ Full | GFM, frontmatter, tables, task lists | Documentation, READMEs, blogs |
-| `.mdx` | ✅ Full | Above + JSX components, imports/exports | React docs, interactive content |
-| `.mdd` | ⚠️ Optional | Business documents (see below) | Invoices, proposals, contracts |
+| Extension | Support     | Features                                | Use Case                        |
+| --------- | ----------- | --------------------------------------- | ------------------------------- |
+| `.md`     | ✅ Full      | GFM, frontmatter, tables, task lists    | Documentation, READMEs, blogs   |
+| `.mdx`    | ✅ Full      | Above + JSX components, imports/exports | React docs, interactive content |
+| `.mdc`    | ✅ Full      | Markdown Components (Nuxt Content)      | Nuxt Content, Vue documentation |
+| `.mdd`    | ⚠️ Optional | Business documents (see below)          | Invoices, proposals, contracts  |
+
+### MDC Support
+
+This formatter includes **full support for `.mdc` files** and MDC (Markdown Components) syntax via `remark-mdc`. MDC is a superset of Markdown developed by Nuxt that allows you to use Vue-like components.
+
+**MDC Features:**
+
+```markdown
+<!-- Block components -->
+::card
+This is card content with **formatting**.
+::
+
+<!-- Inline components -->
+This is text with an :icon{name="rocket"} inline component.
+
+<!-- Props and attributes -->
+![Image]{.rounded width="400"}
+
+<!-- Slots and nesting -->
+::alert{type="warning"}
+This is a warning message!
+::
+```
+
+**Perfect for:**
+- Nuxt Content projects
+- Component-driven documentation
+- Interactive markdown content
+- Vue.js documentation sites
+
+**File Usage:**
+- `.mdc` extension - Dedicated MDC files (like `.mdx` for JSX)
+- MDC syntax also works in `.md` and `.mdx` files
 
 ### MDD Support
 
@@ -106,7 +153,7 @@ This formatter can **optionally** format `.mdd` files if you install the [MDD pa
 
 ```bash
 # Install MDD support
-pnpm add mdd
+pnpm add @entro314labs/mdd
 
 # Now .mdd files will be formatted
 pnpm run format
@@ -122,10 +169,74 @@ pnpm run format
 markdownfix format [files...]   # Format and fix markdown files
 markdownfix check [files...]    # Check without writing changes
 markdownfix lint [files...]     # Lint for issues only
+markdownfix nuclear [files...]  # 🚀 Run ALL linters and fixers
 markdownfix init               # Create .remarkrc.js config
 markdownfix setup              # Create example content structure
 ```
 
+### 🚀 Nuclear Mode
+
+The `nuclear` command runs a comprehensive 4-step workflow that applies **all** available linters and fixers:
+
+1. **Remark Formatting** - Auto-fix markdown syntax
+2. **Remark Linting** - Validate markdown rules (40+ rules)
+3. **ESLint Auto-fix** - Fix JavaScript/JSX in code blocks
+4. **ESLint Linting** - Validate code quality
+
+**Perfect for:**
+
+- Pre-commit hooks
+- CI/CD pipelines
+- Major cleanup sessions
+- Ensuring everything is pristine
+
+**Usage:**
+
+```bash
+# Run on all markdown files
+markdownfix nuclear
+
+# Run on specific directory
+markdownfix nuclear --glob "docs/**/*.{md,mdx}"
+
+# Add to package.json
+{
+  "scripts": {
+    "precommit": "markdownfix nuclear"
+  }
+}
+```
+
+**Example Output:**
+
+```
+🚀 NUCLEAR MODE ACTIVATED
+
+Processing 15 file(s) with comprehensive workflow...
+
+Step 1/4: Running remark formatting...
+  ✓ Remark formatting completed
+
+Step 2/4: Running remark linting...
+  ✓ Remark linting passed
+
+Step 3/4: Running ESLint auto-fix...
+  ✓ ESLint auto-fix completed
+
+Step 4/4: Running ESLint linting...
+  ✓ ESLint linting passed
+
+════════════════════════════════════════════════════════════
+NUCLEAR MODE SUMMARY
+════════════════════════════════════════════════════════════
+✓ Remark Format        PASS   Formatted 15/15 files
+✓ Remark Lint          PASS   Linted 15 files
+✓ ESLint Fix           PASS   Auto-fixed code blocks
+✓ ESLint Lint          PASS   All code blocks valid
+════════════════════════════════════════════════════════════
+🎉 All checks passed! Your markdown is pristine.
+```
+
 ### Command Aliases
 
 The CLI is available via two commands:
@@ -177,11 +288,15 @@ pnpm run format         # Apply fixes using remark-cli
 pnpm run format:check   # Preview changes
 
 # Linting
-pnpm run lint           # Check compliance
+pnpm run lint           # Remark-lint only
+pnpm run lint:eslint    # ESLint + MDX only
+pnpm run lint:eslint:fix # ESLint auto-fix
+pnpm run lint:all       # Both remark and ESLint
 
 # Combined
-pnpm run process        # Format then lint
-pnpm run process:safe   # Dry-run first, then process
+pnpm run process        # Format then lint all
+pnpm run process:safe   # Dry-run first, then lint all
+pnpm run nuclear        # 🚀 Run ALL linters and fixers
 pnpm test               # Same as process:safe
 
 # Utilities
@@ -209,11 +324,13 @@ markdownfix/
 ### `.remarkrc.js`
 
 Central configuration defining:
+
 - All formatting rules
 - Plugin chain order
 - Lint rule settings
 
 **Plugin order is critical:**
+
 1. `remark-frontmatter` - Parse YAML/TOML
 2. `remark-gfm` - GitHub Flavored Markdown
 3. `remark-mdx` - MDX support (conditional)
@@ -223,6 +340,7 @@ Central configuration defining:
 ### `.remarkignore`
 
 Files excluded from processing:
+
 - `README.md`
 - `CHANGELOG.md`
 - `LICENSE`
@@ -246,6 +364,7 @@ author: Optional but recommended
 **Cause**: No markdown files found or all files excluded
 
 **Solution**:
+
 - Ensure markdown files exist in `content/` directory
 - Check `.remarkignore` patterns
 - Verify correct file extensions (`.md`, `.mdx`)
@@ -255,6 +374,7 @@ author: Optional but recommended
 **Cause**: Some rules require manual fixes (duplicate headings, broken links)
 
 **Solution**:
+
 - Read console output for specific violations
 - Manually fix reported issues
 - Use `pnpm run format:check` to separate formatting from lint errors
@@ -264,6 +384,7 @@ author: Optional but recommended
 **Cause**: Invalid JSX syntax
 
 **Solution**:
+
 - Verify JSX is valid JavaScript
 - Check all tags are properly closed
 - Ensure React components use `<Component />` not `<Component>`
@@ -285,46 +406,69 @@ pnpm run process:safe
 
 **Disable VS Code remark extensions** - they may conflict with this opinionated configuration. Always use command line processing.
 
-## Two Projects, One Ecosystem
+## Entro314 Labs Markdown Ecosystem
+
+markdownfix is part of a comprehensive markdown ecosystem. For complete documentation, see [PROJECT\_ECOSYSTEM.md](../PROJECT_ECOSYSTEM.md).
+
+### Companion Projects
+
+#### 📄 [MDD (Markdown Document)](https://github.com/entro314-labs/mdd)
 
-This repository focuses on **developer documentation** (READMEs, technical docs, blogs).
+**The missing document layer for the AI-to-Office pipeline.**
 
-For **business documents** (invoices, proposals, letters, contracts), we have a companion project:
+Semantic document format for professional business documents:
 
-### 📄 [MDD (Markdown Document)](https://github.com/entro314-labs/mdd)
+- **Semantic directives**: `::letterhead`, `::signature-block`, `::header`, `::footer`
+- **Multi-format output**: HTML, PDF, DOCX from single source
+- **AI workflow integration**: ChatGPT/Claude markdown → professional documents
+- **Zero configuration**: Professional styling built-in
+- **200+ document types**: Comprehensive business document catalog
+- **Version control friendly**: Plain text `.mdd` files
 
-MDD extends markdown with business-focused features:
+**Installation**: `npm install -g @entro314labs/mdd`
 
-- Letterheads and headers/footers
-- Signature blocks
-- Contact information blocks
-- Professional PDF/DOCX output
-- Invoice and proposal templates
+**Quick start**:
 
 ```bash
-# Quick example
-cd ../mdd
-pnpm run preview examples/invoice.mdd
-# Opens professional HTML invoice in browser
+# Preview business document
+mdd-preview document.mdd
+
+# Or use with npx
+npx mdd-preview examples/invoice.mdd
 ```
 
-**When to use which:**
+markdownfix can **optionally format `.mdd` files** by installing MDD as a dependency.
+
+#### 🖥️ [Anasa](https://github.com/entro314-labs/anasa)
+
+Desktop knowledge management application with MDD integration:
+
+- Bidirectional linking and graph visualization
+- TipTap WYSIWYG editor
+- **First GUI editor for MDD format**
+- Create professional business documents inside your knowledge base
+- Live preview and PDF export
 
-| Use Case | Project | File Type |
-|----------|---------|-----------|
-| README files | Markdown Formatter | `.md` |
-| Technical docs | Markdown Formatter | `.md` |
-| Blog posts | Markdown Formatter | `.md` / `.mdx` |
-| React documentation | Markdown Formatter | `.mdx` |
-| **Business letters** | **MDD** | `.mdd` |
-| **Invoices** | **MDD** | `.mdd` |
-| **Proposals** | **MDD** | `.mdd` |
-| **Contracts** | **MDD** | `.mdd` |
+**Status**: MDD integration planned ([see integration spec](../anasa/MDD_INTEGRATION_SPEC.md))
+
+### When to Use Which
+
+| Document Type                  | Use         | File Extension | Package                     |
+| ------------------------------ | ----------- | -------------- | --------------------------- |
+| README files                   | markdownfix | `.md`          | `@entro314labs/markdownfix` |
+| Technical documentation        | markdownfix | `.md`          | `@entro314labs/markdownfix` |
+| Blog posts                     | markdownfix | `.md` / `.mdx` | `@entro314labs/markdownfix` |
+| React component docs           | markdownfix | `.mdx`         | `@entro314labs/markdownfix` |
+| **Business letters**           | **MDD**     | **`.mdd`**     | **`@entro314labs/mdd`**     |
+| **Invoices**                   | **MDD**     | **`.mdd`**     | **`@entro314labs/mdd`**     |
+| **Proposals**                  | **MDD**     | **`.mdd`**     | **`@entro314labs/mdd`**     |
+| **Contracts**                  | **MDD**     | **`.mdd`**     | **`@entro314labs/mdd`**     |
+| Knowledge base + business docs | Anasa + MDD | `.md` + `.mdd` | Desktop app                 |
 
 ## Documentation
 
-- **[COMPREHENSIVE-GUIDE.md](COMPREHENSIVE-GUIDE.md)** - Detailed technical guide
 - **[content/guides/style-guide.md](content/guides/style-guide.md)** - Style specifications
+- **[ESLINT_INTEGRATION.md](ESLINT_INTEGRATION.md)** - ESLint + MDX integration guide
 
 ## Tech Stack
 
@@ -332,10 +476,13 @@ pnpm run preview examples/invoice.mdd
 - **Unified** - AST transformation
 - **GFM** - GitHub Flavored Markdown
 - **MDX** - JSX in markdown
+- **MDC** - Markdown Components (Nuxt Content)
+- **ESLint** - JavaScript/JSX linting in code blocks
 
 ## Contributing
 
 This is an opinionated formatter with specific style decisions. Contributions should:
+
 - Maintain existing formatting rules
 - Add value for developer documentation
 - Not break existing lint rules

package/cli.js

@@ -17,8 +17,9 @@ import remarkStringify from 'remark-stringify';
 import fs from 'fs/promises';
 import path from 'path';
 import { glob } from 'glob';
+import { execSync } from 'child_process';
 
-const MARKDOWN_EXTENSIONS = ['md', 'mdx', 'mdd'];
+const MARKDOWN_EXTENSIONS = ['md', 'mdx', 'mdc', 'mdd'];
 
 // Import configuration from .remarkrc.js
 let remarkConfig;
@@ -44,6 +45,7 @@ COMMANDS:
   format [files]     Format markdown files (writes changes)
   check [files]      Check formatting without writing changes
   lint [files]       Lint markdown files (no formatting)
+  nuclear [files]    🚀 Run ALL linters and fixers (remark + ESLint)
   init               Create .remarkrc.js configuration file
   setup              Create example content structure
 
@@ -52,6 +54,7 @@ OPTIONS:
   --version, -v      Show version number
   --quiet, -q        Suppress output except errors
   --glob <pattern>   Use glob pattern (e.g., "**/*.md")
+  --nuclear          Run complete lint+fix workflow (alias for nuclear command)
 
 EXAMPLES:
   # Format all markdown files in current directory
@@ -66,9 +69,22 @@ EXAMPLES:
   # Format quietly
   markdownfix format --quiet
 
+  # 🚀 Nuclear option - fix EVERYTHING
+  markdownfix nuclear
+  markdownfix format --nuclear
+
   # Initialize configuration
   markdownfix init
 
+NUCLEAR MODE:
+  The nuclear command runs a comprehensive fix workflow:
+  1. Remark formatting (auto-fix markdown syntax)
+  2. Remark linting (validate markdown rules)
+  3. ESLint auto-fix (fix JavaScript in code blocks)
+  4. ESLint linting (validate code quality)
+
+  Perfect for: CI/CD, pre-commit hooks, major cleanups
+
 For more information, visit: https://github.com/entro314-labs/markdownfix
 `);
 }
@@ -168,6 +184,145 @@ async function processFiles(files, options = {}) {
   return { hasErrors, processedCount, totalFiles: files.length };
 }
 
+/**
+ * Run nuclear mode - comprehensive fix workflow
+ * Executes: remark format -> remark lint -> eslint fix -> eslint lint
+ */
+async function runNuclearMode(files, options = {}) {
+  const { quiet = false } = options;
+  const hasEslint = await checkEslintAvailable();
+
+  if (!quiet) {
+    console.log('\n🚀 NUCLEAR MODE ACTIVATED\n');
+    console.log(`Processing ${files.length} file(s) with comprehensive workflow...\n`);
+  }
+
+  let overallSuccess = true;
+  const steps = [];
+
+  // Step 1: Remark formatting
+  if (!quiet) console.log('Step 1/4: Running remark formatting...');
+  try {
+    const result = await processFiles(files, { write: true, quiet: true });
+    steps.push({
+      name: 'Remark Format',
+      success: !result.hasErrors,
+      details: `Formatted ${result.processedCount}/${result.totalFiles} files`
+    });
+    if (result.hasErrors) overallSuccess = false;
+    if (!quiet) console.log(`  ✓ Remark formatting completed\n`);
+  } catch (error) {
+    steps.push({ name: 'Remark Format', success: false, details: error.message });
+    overallSuccess = false;
+    if (!quiet) console.log(`  ✗ Remark formatting failed: ${error.message}\n`);
+  }
+
+  // Step 2: Remark linting
+  if (!quiet) console.log('Step 2/4: Running remark linting...');
+  try {
+    const result = await processFiles(files, { lintOnly: true, quiet: true });
+    steps.push({
+      name: 'Remark Lint',
+      success: !result.hasErrors,
+      details: `Linted ${result.totalFiles} files`
+    });
+    if (result.hasErrors) {
+      if (!quiet) console.log('  ⚠️  Remark linting found issues (check output above)\n');
+      overallSuccess = false;
+    } else {
+      if (!quiet) console.log(`  ✓ Remark linting passed\n`);
+    }
+  } catch (error) {
+    steps.push({ name: 'Remark Lint', success: false, details: error.message });
+    overallSuccess = false;
+    if (!quiet) console.log(`  ✗ Remark linting failed: ${error.message}\n`);
+  }
+
+  // Step 3 & 4: ESLint (only if available)
+  if (hasEslint) {
+    // Step 3: ESLint auto-fix
+    if (!quiet) console.log('Step 3/4: Running ESLint auto-fix...');
+    try {
+      const fileList = files.join(' ');
+      const eslintCmd = `npx eslint --ext .md,.mdx,.mdc,.mdd --fix ${fileList}`;
+
+      try {
+        execSync(eslintCmd, {
+          stdio: quiet ? 'pipe' : 'inherit',
+          cwd: process.cwd()
+        });
+        steps.push({ name: 'ESLint Fix', success: true, details: 'Auto-fixed code blocks' });
+        if (!quiet) console.log(`  ✓ ESLint auto-fix completed\n`);
+      } catch (eslintError) {
+        // ESLint returns non-zero even if it fixes issues
+        steps.push({ name: 'ESLint Fix', success: false, details: 'Some issues could not be auto-fixed' });
+        if (!quiet) console.log(`  ⚠️  ESLint auto-fix completed with warnings\n`);
+      }
+    } catch (error) {
+      steps.push({ name: 'ESLint Fix', success: false, details: error.message });
+      if (!quiet) console.log(`  ✗ ESLint auto-fix failed: ${error.message}\n`);
+    }
+
+    // Step 4: ESLint linting
+    if (!quiet) console.log('Step 4/4: Running ESLint linting...');
+    try {
+      const fileList = files.join(' ');
+      const eslintCmd = `npx eslint --ext .md,.mdx,.mdc,.mdd ${fileList}`;
+
+      execSync(eslintCmd, {
+        stdio: quiet ? 'pipe' : 'inherit',
+        cwd: process.cwd()
+      });
+      steps.push({ name: 'ESLint Lint', success: true, details: 'All code blocks valid' });
+      if (!quiet) console.log(`  ✓ ESLint linting passed\n`);
+    } catch (eslintError) {
+      steps.push({ name: 'ESLint Lint', success: false, details: 'Linting issues found' });
+      overallSuccess = false;
+      if (!quiet) console.log(`  ⚠️  ESLint linting found issues\n`);
+    }
+  } else {
+    if (!quiet) {
+      console.log('Step 3/4: Skipping ESLint (not installed)');
+      console.log('  ℹ️  Install ESLint with: npm install -D eslint eslint-plugin-mdx\n');
+      console.log('Step 4/4: Skipping ESLint linting\n');
+    }
+    steps.push({ name: 'ESLint Fix', success: true, details: 'Skipped (not installed)' });
+    steps.push({ name: 'ESLint Lint', success: true, details: 'Skipped (not installed)' });
+  }
+
+  // Summary
+  if (!quiet) {
+    console.log('═'.repeat(60));
+    console.log('NUCLEAR MODE SUMMARY');
+    console.log('═'.repeat(60));
+    steps.forEach(step => {
+      const icon = step.success ? '✓' : '✗';
+      const status = step.success ? 'PASS' : 'FAIL';
+      console.log(`${icon} ${step.name.padEnd(20)} ${status.padEnd(6)} ${step.details}`);
+    });
+    console.log('═'.repeat(60));
+    if (overallSuccess) {
+      console.log('🎉 All checks passed! Your markdown is pristine.\n');
+    } else {
+      console.log('⚠️  Some issues remain. Review the output above.\n');
+    }
+  }
+
+  return { success: overallSuccess, steps };
+}
+
+/**
+ * Check if ESLint is available in the project
+ */
+async function checkEslintAvailable() {
+  try {
+    execSync('npx eslint --version', { stdio: 'pipe' });
+    return true;
+  } catch {
+    return false;
+  }
+}
+
 /**
  * Initialize .remarkrc.js configuration
  */
@@ -250,6 +405,7 @@ async function main() {
   // Parse options
   const options = {
     quiet: commandArgs.includes('--quiet') || commandArgs.includes('-q'),
+    nuclear: commandArgs.includes('--nuclear'),
     glob: null
   };
 
@@ -274,6 +430,14 @@ async function main() {
         console.log('No markdown files found');
         return;
       }
+
+      // Check for --nuclear flag
+      if (options.nuclear) {
+        const result = await runNuclearMode(files, { quiet: options.quiet });
+        process.exit(result.success ? 0 : 1);
+        break;
+      }
+
       if (!options.quiet) {
         console.log(`Formatting ${files.length} file(s)...`);
       }
@@ -331,6 +495,17 @@ async function main() {
       break;
     }
 
+    case 'nuclear': {
+      const files = await getFiles(fileArgs, options.glob);
+      if (files.length === 0) {
+        console.log('No markdown files found');
+        return;
+      }
+      const result = await runNuclearMode(files, { quiet: options.quiet });
+      process.exit(result.success ? 0 : 1);
+      break;
+    }
+
     default:
       console.error(`Unknown command: ${command}`);
       console.error('Run "markdownfix --help" for usage information');

package/eslint.config.js

@@ -0,0 +1,82 @@
+/**
+ * ESLint configuration for MDX files
+ * Uses eslint-plugin-mdx with existing remark-lint configuration
+ *
+ * This integrates with the existing .remarkrc.js file to provide:
+ * - JSX/JavaScript linting inside MDX code blocks
+ * - IDE integration for better developer experience
+ * - Unified linting workflow alongside remark-lint
+ */
+
+import * as mdxPlugin from 'eslint-plugin-mdx';
+
+export default [
+  {
+    // Ignore common directories
+    // Replaces .eslintignore file (no longer supported in ESLint 9)
+    ignores: [
+      'node_modules/**',
+      'dist/**',
+      'build/**',
+      '.next/**',
+      'coverage/**',
+      'pnpm-lock.yaml',
+      '**/*.config.js',
+      '**/*.config.mjs',
+      'README.md',
+      'CHANGELOG.md',
+      'LICENSE',
+      'PUBLISHING.md',
+      'ESLINT_INTEGRATION.md',
+      '.cache/**',
+      '.remark-cache/**'
+    ]
+  },
+
+  // MDX/MDC files configuration
+  {
+    name: 'custom/mdx/recommended',
+    files: ['**/*.{md,mdx,mdc,mdd}'],
+    ...mdxPlugin.flat,
+    processor: mdxPlugin.createRemarkProcessor({
+      lintCodeBlocks: true, // Enable linting of code blocks
+      languageMapper: {}    // Use default language mappings
+    }),
+    rules: {
+      // MDX-specific rules from eslint-plugin-mdx
+      // The remark-lint rules from .remarkrc.js will be automatically used
+      'mdx/remark': 'error',
+    },
+    settings: {
+      'mdx/code-blocks': true,  // Enable code block linting
+      'mdx/language-mapper': {} // Use default mappings
+    }
+  },
+
+  // Code blocks in MDX/MDC (optional - for stricter linting)
+  {
+    name: 'custom/mdx/code-blocks',
+    files: ['**/*.{md,mdx,mdc,mdd}'],
+    ...mdxPlugin.flatCodeBlocks,
+    languageOptions: {
+      globals: {
+        console: 'readonly',
+        process: 'readonly',
+        require: 'readonly',
+        module: 'readonly',
+        exports: 'readonly',
+        __dirname: 'readonly',
+        __filename: 'readonly',
+      }
+    },
+    rules: {
+      ...mdxPlugin.flatCodeBlocks.rules,
+      // Add JavaScript rules for code blocks
+      'no-var': 'error',
+      'prefer-const': 'error',
+      'no-unused-vars': 'warn',
+      // Allow common globals in documentation examples
+      'no-undef': 'off',
+    }
+  }
+];

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@entro314labs/markdownfix",
-  "version": "0.0.6",
-  "description": "Opinionated markdown formatter and linter for MD, MDD and MDX files using Remark/Unified ecosystem",
+  "version": "0.0.10",
+  "description": "Opinionated markdown formatter and linter for MD, MDX, MDC, and MDD files using Remark/Unified ecosystem",
   "type": "module",
   "repository": {
     "type": "git",
@@ -14,9 +14,11 @@
   "files": [
     ".remarkrc.js",
     ".remarkignore",
+    "eslint.config.js",
     "setup.js",
     "cli.js",
     "README.md",
+    "ESLINT_INTEGRATION.md",
     "LICENSE"
   ],
   "bin": {
@@ -27,6 +29,7 @@
   "keywords": [
     "markdown",
     "mdx",
+    "mdc",
     "mdd",
     "linter",
     "formatter",
@@ -35,11 +38,16 @@
     "unified",
     "markdownfix",
     "markdown-linter",
+    "markdown-components",
+    "nuxt-content",
     "opinionated"
   ],
   "author": "Dominikos Pritis",
   "license": "MIT",
   "devDependencies": {
+    "eslint": "^9.38.0",
+    "eslint-plugin-mdx": "^3.6.2",
+    "eslint-plugin-react": "^7.37.5",
     "markdown-link-check": "^3.14.1",
     "remark-cli": "^12.0.1"
   },
@@ -49,7 +57,7 @@
   "dependencies": {
     "@adobe/remark-gridtables": "^3.0.15",
     "@code-dot-org/remark-plugins": "^2.0.0",
-    "@entro314labs/mdd": "^0.0.6",
+    "@entro314labs/remark-mdd": "^0.0.10",
     "@theguild/remark-mermaid": "^0.3.0",
     "fumadocs-docgen": "^3.0.2",
     "glob": "^11.0.3",
@@ -118,11 +126,15 @@
   },
   "scripts": {
     "lint": "remark . --quiet --frail",
+    "lint:eslint": "eslint --ext .md,.mdx,.mdc,.mdd .",
+    "lint:eslint:fix": "eslint --ext .md,.mdx,.mdc,.mdd --fix .",
+    "lint:all": "pnpm run lint && pnpm run lint:eslint",
     "format": "remark . --output --quiet",
     "format:check": "remark . --quiet",
-    "check-links": "markdown-link-check **/*.{md,mdx,mdd}",
-    "process": "pnpm run format && pnpm run lint",
-    "process:safe": "pnpm run format:check && pnpm run lint",
+    "check-links": "markdown-link-check **/*.{md,mdx,mdc,mdd}",
+    "process": "pnpm run format && pnpm run lint:all",
+    "process:safe": "pnpm run format:check && pnpm run lint:all",
+    "nuclear": "node cli.js nuclear",
     "clean-cache": "rm -rf .remark-cache",
     "test": "pnpm run process:safe"
   }