chore: update tailwind example to v4

[birkskyum]

This PR adopts tailwind 4, with the tried and tested postcss config that we know work.

This is a safe way of doing things, in comparison to using the new tailwind vite plugin:

• Tailwind CSS bug repro #1748
• Upgrade Tailwind CSS example to v4 #1747

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0445820

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[netlify]

✅ Deploy Preview for solid-start-landing-page ready!

Name	Link
🔨 Latest commit	0445820
🔍 Latest deploy log	https://app.netlify.com/sites/solid-start-landing-page/deploys/67a9fe6de9a1660009a84361
😎 Deploy Preview	https://deploy-preview-1787--solid-start-landing-page.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[pkg-pr-new]

Open in Stackblitz

More templates

• example-bare
• example-basic
• example-experiments
• example-hackernews
• example-notes
• example-todomvc
• example-with-auth
• example-with-authjs
• example-with-drizzle
• example-with-mdx
• example-with-solid-styled
• example-with-prisma
• example-with-tailwindcss
• example-with-trpc
• example-with-unocss
• example-with-vitest

npm i https://pkg.pr.new/@solidjs/start@1787

commit: 0445820

[DaniGuardiola]

Hi @birkskyum thank you.

A few observations:

• The bug originally preventing the vite plugin from working has been fixed.
• The other bug causing & to be wrongly processed is NOT related to vite, it happens independently of whether vite or postcss is used.
• The postcss method is outdated and no longer the main recommended approach (vite is instead). It's probably slower too.
• I think the example should be updated to the vite setup since the only actual vite-related bug was solved. The other issue should be fixed independently.
• In fact, I think the Tailwind example should be reverted to v3 for now, as it is currently broken and new users will get a broken starting boilerplate. Then, once fixed, it should be updated to the recommended vite setup.