Wondering about static analysis on content script output and AST usage in Plasmo
Hi, hope you're all well
I use Plasmo at my workplace where we have heaps of content scripts with unique config objects returned (often with different matches arrays). To make the code more readable and easy to understand I was going to introduce some changes to dynamically populate the URL matches list with common URLs that are used for each extension.
Recently I discovered that Plasmo statically analyses these files, causing errors when trying to dynamically populate the configuration.
Why does Plasmo use a custom AST parser for the config?
I use Plasmo at my workplace where we have heaps of content scripts with unique config objects returned (often with different matches arrays). To make the code more readable and easy to understand I was going to introduce some changes to dynamically populate the URL matches list with common URLs that are used for each extension.
Recently I discovered that Plasmo statically analyses these files, causing errors when trying to dynamically populate the configuration.
Why does Plasmo use a custom AST parser for the config?
