I do find this idea intriguing. I’ve started a ticket in our repository and will look into it a little more. Just some thoughts about this. —
themeblvd.js or in any enqueue’d script in quite the same way. So, we’d be effectively somewhat abandoning WordPress’s system for scripts and creating our own system.
Now, contrary to what I said above, an alternate approach that the framework could accomplish what you’re suggesting with still enque’ing a file would be to register locals within the PHP that have true/false booleans for our different plugins and check for them in the
So, I’m not quite sure how to handle what you’re suggesting without causing other issues or making other things more confusing. With a framework like this, there are just so many scripts coming into play, and I’m just trying to keep them as tight to the WordPress-intended system as possible. But I will take a look at what you’re suggesting and see how this could possibly be incorporated within the global config filter and possibly not effect other things.