matchUtilities breaks intellisense about tailwindcss-intellisense HOT 2 CLOSED

Hey so the reason Intellisense is breaking with the above config is that parseColor returns null when passed a color that can't be parsed. For example, inherit is a value in our color palette but it's not a "real" color. The code is then attempting to destructure the null return value which then throws an error.

Intellisense calls this function with every value listed in values and isn't catching the error which then breaks the extension.

I've merged in a fix for this in our pre-release build which you can switch to in VS Code if you go to the extension's page. (It'll take around 10 minutes for the build to be available — you may need to reload VSCode for it to detect the update)

In the meantime, if you don't want to use the pre-release build, the best way to fix this is check if parseColor(…) returns null and embed the value directly in the CSS if so. One way to do this is using the nullish coalescing operator (??) like so:

matchUtilities(
    {
        'text-stroke': (value) => {
            const { color } = parseColor(value) ?? { color: value }

            return {
                '-webkit-text-stroke': `1px rgb(${color[0]} ${color[1]} ${color[2]})`,
            }
        },
    },
    { values: flattenColorPalette(theme('colors')), type: 'color' }
)

from tailwindcss-intellisense.

Thank you!

from tailwindcss-intellisense.