Incompatibility with some coding styles

Hello!

I’m a fan of putting a space after the opening and before the closing function parens (for multiple reasons), and it seems like this plugin is not compatible with that type of coding style because it’s using (too) specific sub-string to match when collecting the properties, ie var(--.

Perhaps something like this would make it more forgiving?

Declaration (node, {Declaration}) {
	// bail early
	if (node[processed]) return

	let matches = node.value.match(/var\(\s*[\w\d-]+\s*\)/g);

	if (!matches) return;

	let props = matches.map(v => v.match(/var\(\s*([\w\d-]+)\s*\)/)[1])

	// ...
}

Disclaimer: My regex-fu is questionable 😁

[argyleink]

released and fixed in 1.0.2 👍🏻 thanks for the help!

[kucrut]

@argyleink I took a stab at this and issued a PR: https://github.com/GoogleChromeLabs/postcss-jit-props/pull/6