Migrate remaining jscodeshift to jssg

[ShadiBitaraf]

Overview

Official Nuxt codemods for migrating from v3 to v4, automating breaking change transformations through 5 specialized codemods that handle API updates and deprecated patterns.

Key Features

• Path Normalization: Updates nuxt.hook('builder:watch') to use absolute paths
• Data Fetching Updates: Transforms null checks to undefined for useAsyncData/useFetch, adds { deep: true } options
• Template Migration: Converts addTemplate from src property to getContents function
• Dedupe Modernization: Changes boolean dedupe values to string format in refresh() calls
• Registry Ready: Available via npx codemod@latest @nuxt-v3-to-v4

Impact

• Automated Migration: Handles all major v3 → v4 breaking changes programmatically
• Tested Transformations: Each codemod validated with input/output test cases
• Production Safe: Preserves functionality while updating to v4 patterns

Files Modified

• Codemods: 5 transformation scripts handling specific breaking changes
• Utils: Modular utilities (ast-utils.ts, import-utils.ts, nuxt-patterns.ts)
• Tests: Input/expected output pairs for each transformation
• Config: codemod.yaml, workflow.yaml, package.json for Registry integration
• Docs: Installation and usage instructions

[mohebifar]

Suggested change

	export function hasContent<T extends Record<string, any>>(
	export function hasContent<T extends TypesMap>(

[mohebifar]

We shouldn't encourage string ops, and this is a bad practice imo. This is also a duplicate check. You're already performing an ast-based search later.

[mohebifar]

This shouldn't be file-wide.

Imagine you have:

function X() {
  const { data: listData, error: listError } = useFetch(
    () => client.value.v1.lists.fetch(),
    {
      default: () => shallowRef(),
    }
  );
}


function Y() {
  const listData = ...

  
  if (userData.value === null) {
  }
}

listData is marked as dataErrorVar in the entire file, while in function Y, we don't care about this var.