npm run dev fails silently when using npm — playground package.json uses "my-module": "latest" instead of "file:.."

Description

When scaffolding a new Nuxt module with npm create nuxt -- -t module my-module and using npm (not pnpm),
the playground cannot resolve the local module, causing the plugin to never be injected and myModule
to be ignored in nuxt.config.ts — with no error in the console.

Root cause

The generated playground/package.json has:

"dependencies": {
  "my-module": "latest"
}

Steps to reproduce

1. npm create nuxt -- -t module my-module
2. cd my-module
3. npm run dev
4. Plugin from src/runtime/plugin.ts is never injected — no error shown

Fix

Change playground/package.json to use "file:..":

"dependencies": {
  "my-module": "file:.."
}

Environment

• npm: 11.10.0
• nuxt: 4.3.1
• @nuxt/module-builder: 1.0.2
• OS: Windows 11

Start with the generated playground/package.json and compare its dependency entry with the npm reproduction steps. Verify the generated package points to the local module, then run npm run dev and confirm that the plugin from src/runtime/plugin.ts is injected and myModule is no longer ignored.