Can this skill detect different package managers?

Yes, it automatically identifies whether the project uses npm, yarn, pnpm, or bun by checking for existing lockfiles like yarn.lock or pnpm-lock.yaml.

How do I fix 'Cannot find module #imports' errors?

This skill resolves that error by running the Nuxt preparation command to regenerate the necessary internal type mappings.

Does it support Git worktrees?

Yes, the skill includes specialized logic to handle isolated node_modules and .nuxt directories required when working across multiple Git worktrees.

What does 'npx nuxt prepare' do in this skill?

It generates the .nuxt directory and type definitions required for auto-imports and path aliases to work correctly in TypeScript.

How does it help with VS Code setup?

It provides the recommended settings for the Volar extension, including hybrid mode and workspace TypeScript SDK paths, to ensure a smooth IDE experience.

Nuxt Project Setup

Name: Nuxt Project Setup
Author: martin-janci

bymartin-janci

•

Developer Tools

Automates the configuration, dependency installation, and TypeScript environment preparation for Nuxt 3 and Vue projects.

About

The nuxt-setup skill streamlines the initialization and maintenance of Nuxt 3 environments by handling package manager detection, dependency installation, and the generation of essential Nuxt types. It ensures full TypeScript support by configuring the Language Server Protocol (LSP), resolving path aliases like #imports, and verifying builds with vue-tsc. Whether you are working on a fresh clone, managing git worktrees, or troubleshooting 'module not found' errors, this skill provides a standardized workflow to get your development environment production-ready.

Key Features

Configures VS Code Volar and Neovim LSP settings
1 GitHub stars
Auto-detects package managers (npm, yarn, pnpm, bun)
Validates TypeScript health using vue-tsc
Generates Nuxt types and resolves #imports aliases
Automates setup for Git worktrees and environment variables

Use Cases

Fixing broken TypeScript path aliases or missing auto-import types
Configuring local development environments for VS Code or Neovim
Setting up a Nuxt 3 project from a fresh repository clone

About

Key Features

Configures VS Code Volar and Neovim LSP settings
1 GitHub stars
Auto-detects package managers (npm, yarn, pnpm, bun)
Validates TypeScript health using vue-tsc
Generates Nuxt types and resolves #imports aliases
Automates setup for Git worktrees and environment variables

Use Cases

Fixing broken TypeScript path aliases or missing auto-import types
Configuring local development environments for VS Code or Neovim
Setting up a Nuxt 3 project from a fresh repository clone