-
-
Notifications
You must be signed in to change notification settings - Fork 76
Description
Which project does this relate to?
Start
Describe the bug
I ran pnpx create-start-app@latest
(0.22.2 is current version)
This is my configuration:
│
◇ What would you like to name your project?
│ example-site-temp
│
◇ Would you like to use Tailwind CSS?
│ Yes
│
◇ Select toolchain
│ ESLint
│
◇ What add-ons would you like for your project?
│ Form, Query
│
◇ Would you like any examples?
│ none
To force PNPM to do a fresh install, delete the pnpm lock file. Since I only just did an initial install the presence of a lock file should not make a difference.
Run pnpm i
and you get this "unmet peer" message:
WARN Issues with peer dependencies found
example-site-temp
└─┬ @tanstack/react-start 1.132.7
├── ✕ unmet peer vite@>=7.0.0: found 6.3.6
└─┬ @tanstack/start-plugin-core 1.132.7
└── ✕ unmet peer vite@>=7.0.0: found 6.3.6
In the generated package.json, you see "vite": "^6.3.5"
under "devDependencies" so TanStack Start is using the incorrect version of vite in package.json
Your Example Website or App
https://stackblitz.com/edit/github-3gud9noy?file=package.json
Steps to Reproduce the Bug or Issue
- Run
pnpx create-start-app@latest
- Delete the pnpm lock file
- Run
pnpm i
Expected behavior
There should not be any unmet peer dependency warnings on initial install.
Screenshots or Videos
If you keep the lock file, pnpm doesn't bother resolving the package dependencies

If you delete it though then you get the unmet peer warning:

In the stack-blitz demo, you can also see that if the lock file is deleted there appears to be other peer dependencies that are not met:

Platform
- Start Version: 0.22.2
- OS: Windows 11 using git bash
- Browser: N/A
- Browser Version: N/A
- Bundler: Vite
- Bundler Version: 6.3.5
Additional context
No response