I raised this in #17, but the plugin doesn't yet support custom color palettes.
This PR fixes that by breaking the logic for tailwind shades out into a separate if statement and parsing it accordingly.
I've tested this using the default tailwind color shades, plus custom color palettes and both fit into the same logic. We'd likely just need a documentation update to flag that the tailwind.shades option also enables custom palette support.
This PR also bumps sass-export to 2.1 so that it doesn't try to force load node-sass which will can fail to compile on M1 Macs or Mac OS 12 betas as they require newer versions of node which can't compile the deprecated node-sass.
I raised this in #17, but the plugin doesn't yet support custom color palettes.
This PR fixes that by breaking the logic for tailwind shades out into a separate if statement and parsing it accordingly.
I've tested this using the default tailwind color shades, plus custom color palettes and both fit into the same logic. We'd likely just need a documentation update to flag that the tailwind.shades option also enables custom palette support.
This PR also bumps sass-export to 2.1 so that it doesn't try to force load node-sass which will can fail to compile on M1 Macs or Mac OS 12 betas as they require newer versions of node which can't compile the deprecated node-sass.