Skip to content

Conversation

@haydenbleasel
Copy link
Member

This pull request updates the blog post rendering in the EdgeDB example to use our streamdown library in static mode instead of react-markdown for Markdown parsing and rendering.

@ijjk ijjk added the examples Issue was opened via the examples template. label Nov 23, 2025
Copy link
Contributor

@vercel vercel bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional Suggestion:

A postcss.config.js file is missing. Without it, Next.js will not process Tailwind CSS, and the application will not build correctly or styles will not be applied.

View Details
📝 Patch Details
diff --git a/examples/with-edgedb/postcss.config.js b/examples/with-edgedb/postcss.config.js
new file mode 100644
index 0000000000..12a703d900
--- /dev/null
+++ b/examples/with-edgedb/postcss.config.js
@@ -0,0 +1,6 @@
+module.exports = {
+  plugins: {
+    tailwindcss: {},
+    autoprefixer: {},
+  },
+};

Analysis

Missing postcss.config.js prevents Tailwind CSS processing in with-edgedb example

What fails: The examples/with-edgedb example has tailwindcss and postcss dependencies along with a tailwind.config.js file and Tailwind directives in styles/global.css, but lacks a postcss.config.js file. Without this file, Next.js does not register Tailwind CSS as a PostCSS plugin, so Tailwind directives (@tailwind, @apply, etc.) are never processed.

How to reproduce:

cd examples/with-edgedb
# Build without postcss.config.js
pnpm build
# Styles won't be applied - Tailwind directives are not processed

Expected behavior: The postcss.config.js file should register Tailwind CSS and autoprefixer as PostCSS plugins so that Next.js processes Tailwind directives during the build. Per Next.js Tailwind CSS setup guide, when installing Tailwind CSS with PostCSS, the init command should generate both tailwind.config.js and postcss.config.js files.

Root cause: The PR that added Tailwind to this example (commit 14a4309) installed the dependencies and created tailwind.config.js but did not create the required postcss.config.js file. Next.js's PostCSS loader does not auto-detect Tailwind CSS as a plugin; it requires an explicit configuration file to register it.

Fix on Vercel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

examples Issue was opened via the examples template.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants