Chris Olszewski d87b96bb49 add postcss and tailwindcss to unimplemented files (vercel/turbo#137) ... Note that this doesn't completely close out [vercel/turbo#54](https://github.com/vercel/web-tooling-internal/issues/54) as the [tailwindcss config is optional](https://tailwindcss.com/docs/configuration). I'm digging deeper at additional ways to detect tailwind, but putting this up since it's a strict improvement. ``` olszewski@chriss-mbp next-dev % cargo run -p next-dev -- /tmp/with-tailwindcss-app Compiling next-dev v0.1.0 (/Users/olszewski/code/vercel/the-three-body/crates/next-dev) Finished dev [unoptimized + debuginfo] target(s) in 11.61s Running `/Users/olszewski/code/vercel/the-three-body/target/debug/next-dev /tmp/with-tailwindcss-app` server listening on: http://localhost:3000 error [unimplemented] /private/tmp/with-tailwindcss-app/next.config.js Feature not yet supported Handling the file `next.config.js` is currently unimplemented /private/tmp/with-tailwindcss-app/postcss.config.js Feature not yet supported Handling the file `postcss.config.js` is currently unimplemented /private/tmp/with-tailwindcss-app/tailwind.config.js Feature not yet supported Handling the file `tailwind.config.js` is currently unimplemented [200] / (3045ms) initial compilation 3468ms (3044ms task execution, 48380 tasks) updated in 874ms (8990 tasks) ```		2022-10-20 19:03:17 -04:00
..
next-core	Derive a runtime version from NodeJsEnvironment's node_version (vercel/turbo#15)	2022-10-20 14:46:47 -07:00
next-dev	add postcss and tailwindcss to unimplemented files (vercel/turbo#137)	2022-10-20 19:03:17 -04:00