NuxtN
Nuxt•11mo ago•
4 replies
Zack Plauché

yarn create nuxt -h gives old flags?

On Windows 11, I put in the command yarn create nuxt -h and it gave me the following:
yarn create nuxt -h
yarn create v1.22.22
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...

success Installed "create-nuxt@3.22.5" with binaries:
      - create-nuxt
Create a Nuxt app in seconds (create-nuxt v3.22.5)                                                                                    

USAGE create-nuxt [OPTIONS] [DIR]

ARGUMENTS

  DIR    Project directory

OPTIONS

  --cwd=<directory>    Specify the working directory
     -t, --template    Template name
        -f, --force    Override existing directory
          --offline    Force offline mode
    --preferOffline    Prefer offline mode
       --no-install    Skip installing dependencies
          --gitInit    Initialize git repository
            --shell    Start shell after installation in project directory
   --packageManager    Package manager choice (npm, pnpm, yarn, bun)
      -M, --modules    Nuxt modules to install (comma separated without spaces)


Done in 1.58s.

Then I ran yarn create nuxt . --packageManager yarn --gitInit false to give me:
yarn create v1.22.22
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "create-nuxt@3.22.5" with binaries:
      - create-nuxt
(SKIPPING SOME LINES TO SAVE SPACE FOR DISCORD...)
◐ Installing dependencies...                                                                                                                                         nuxi  10:30:56 AM
! The local project doesn't define a 'packageManager' field. Corepack will now add one referencing yarn@1.22.19+sha1.4ba7fc5c6e704fce2066ecbfb0b0d8976fe62447.
! For more details about this field, consult the documentation at https://nodejs.org/api/packages.html#packagemanager

yarn install v1.22.19
info No lockfile found.
[1/4] Resolving packages...
⠁ (node:48608) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "nuxt > @nuxt/devtools@2.2.1" has unmet peer dependency "vite@>=6.0".
warning "nuxt > @nuxt/devtools > vite-plugin-inspect@11.0.0" has unmet peer dependency "vite@^6.0.0".
warning "nuxt > @nuxt/devtools > vite-plugin-vue-tracer@0.1.1" has unmet peer dependency "vite@^6.0.0".
warning "nuxt > @nuxt/devtools > @nuxt/devtools-kit@2.2.1" has unmet peer dependency "vite@>=6.0".
warning "nuxt > nitropack > openapi-typescript@7.6.1" has unmet peer dependency "typescript@^5.x".
warning "nuxt > @nuxt/devtools > @vue/devtools-core > vite-hot-client@0.2.4" has unmet peer dependency "vite@^2.6.0 || ^3.0.0 || ^4.0.0 || ^5.0.0-0 || ^6.0.0-0".
warning "nuxt > @nuxt/devtools > vite-plugin-inspect > vite-dev-rpc@1.0.7" has unmet peer dependency "vite@^2.9.0 || ^3.0.0-0 || ^4.0.0-0 || ^5.0.0-0 || ^6.0.1".
warning "nuxt > @nuxt/devtools > vite-plugin-inspect > vite-dev-rpc > vite-hot-client@2.0.4" has unmet peer dependency "vite@^2.6.0 || ^3.0.0 || ^4.0.0 || ^5.0.0-0 || ^6.0.0-0".       
[4/4] Building fresh packages...
success Saved lockfile.
$ nuxt prepare
✔ Types generated in .nuxt                                                                                                                                          nuxi  10:31:26 AM
Done in 28.91s.
✔ Installation completed.

Mainly:
! The local project doesn't define a 'packageManager' field. Corepack will now add one referencing yarn@1.22.19+sha1.4ba7fc5c6e704fce2066ecbfb0b0d8976fe62447.

Why does it say it doesn't define a package manager field if I did?

Also, I keep getting a punycode error but I'm not sure what that is.
Was this page helpful?