[CLI] Inconsistent CSS file location when adding Tailwind CSS via npx sv add vs initial setup

[SikandarJODD]

Describe the bug

There is an inconsistency in the CSS file name and location depending on when Tailwind CSS is added to a SvelteKit project:

Scenario 1: Tailwind selected during initial setup

• When selecting Tailwind CSS as an option during npx sv create folder-name
• Result: Creates app.css in the src/ folder

Scenario 2: Tailwind added after initial setup

• When adding Tailwind CSS later using npx sv add tailwindcss
• Result: Creates layout.css in the src/routes/ folder

Reproduction

To reproduce Scenario 1:

npx sv create folder-name
# Select Tailwind CSS during prompts
cd folder-name
# Observe: src/app.css exists

To reproduce Scenario 2:

npx sv create folder-name
# Do NOT select Tailwind CSS during prompts
cd folder-name
npx sv add tailwindcss
# Observe: src/routes/layout.css exists instead

Logs

System Info

System:
    OS: Windows 11 10.0.26100
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12450H
    Memory: 3.88 GB / 15.70 GB
  Binaries:
    Node: 22.17.1 - C:\Program Files\nodejs\node.EXE
    npm: 11.0.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.12.3 - C:\Users\sikandar\AppData\Roaming\npm\pnpm.CMD
    bun: 1.3.0 - C:\Users\sikandar\.bun\bin\bun.EXE

Severity

annoyance

[SikandarJODD]

For Example :

Output 1: Tailwind CSS selected during initial setup
Installation command:

npx sv create test-code --template minimal --types ts --install pnpm

Options selected during prompts:

✅ Tailwind CSS
✅ Prettier

Result: Creates app.css in src/ folder

---

Output 2: Tailwind CSS added after initial setup
Installation command:

npx sv create test-code --template minimal --types ts --install pnpm

Options selected during prompts: none

Then, add Tailwind CSS:

npx sv add tailwindcss

Result: Creates layout.css in src/routes/ folder

[sacrosanctic]

cli/packages/cli/commands/add/workspace.ts

Line 62 in e34d065

const kit = dependencies['@sveltejs/kit'] ? parseKitOptions(resolvedCwd) : undefined;

@jycouet kit is undefined on npx create

[sacrosanctic]

When does the kit package get added?

[jycouet]

Thank you for reporting!!!

The issue is here:

cli/packages/cli/commands/create.ts

Lines 360 to 378 in e34d065

	export async function createVirtualWorkspace({
	cwd,
	template,
	packageManager,
	type
	}: CreateVirtualWorkspaceOptions): Promise<Workspace> {
	const tentativeWorkspace = await createWorkspace({ cwd, packageManager });
	const virtualWorkspace: Workspace = {
	...tentativeWorkspace,
	typescript: type === 'typescript',
	files: {
	...tentativeWorkspace.files,
	viteConfig: type === 'typescript' ? commonFilePaths.viteConfigTS : commonFilePaths.viteConfig,
	svelteConfig:
	type === 'typescript' ? commonFilePaths.svelteConfigTS : commonFilePaths.svelteConfig
	},
	kit: undefined,
	dependencyVersion: () => undefined
	};

Yes, create should set stuff in kit. Need to go now, but will look later if no one did