From fc827b918a70c68cf3dc71ecfcbc0b3dc4381705 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alex=20Bj=C3=B8rlig?= Date: Wed, 26 Aug 2020 13:29:17 +0200 Subject: [PATCH] Added section to troubleshooting MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit In refrence to issue #172, this VS code setting: ``` "search.exclude": { "**/*.js": true }, ``` prevented the Tailwind config from being found ☺️ --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index e3b8c12..6e1fab2 100644 --- a/README.md +++ b/README.md @@ -103,3 +103,4 @@ If you’re having issues getting the IntelliSense features to activate, there a - Ensure that you have a Tailwind config file in your workspace and that this is named `tailwind.config.js` or `tailwind.js`. Check out the Tailwind documentation for details on [creating a config file](https://tailwindcss.com/docs/installation/#3-create-your-tailwind-config-file-optional). - Ensure that the `tailwindcss` module is installed in your workspace, via `npm`, `yarn`, or `pnpm`. Tailwind CSS IntelliSense does not currently support Yarn Plug'n'Play. - If you installed `tailwindcss` or created your config file while your project was already open in Visual Studio Code you may need to reload the editor. You can either restart VS Code entirely, or use the `Developer: Reload Window` command which can be found in the command palette. +- Make sure your VS Code settings (`.vscode/settings.json`) aren't causing the Tailwind config to be excluded from search.