fix: account for spaces when extracting components and directives

[G-Rath]

The current pattern assumes that compiled code will have spaces before and after the = character even though that isn't a requirement of the language for assignments, so it won't work if a build pipeline omits either of those spaces (which is what is happening in one of our applications).

This updated pattern matches any number of spaces on either side of the = character, including zero