Yes but what I mean is, why should you upload something on a production site if you don’t need it?
I, for example, don’t upload the sass files or the uncompressed js version on a server. Those things belong to the git repo. Same thing for development tools, in this case, plugins. If I need it while in dev phase I’ll keep it on the repo but once you’re done you upload only the things you need to make the site run.
Does this make sense to you or do you usually follow a different workflow?
I don’t think plugins would even need to support this option, Kirby would just not load them if the option is set.
If this option would be built into the core, yes, then the plugin developers would not need to add a support for it. Why I added it as a plugin developer suggestion is because in a previous topic we (not me included) decided that it was a bad idea to have an option like that in the core.
But I still think it would be best to have an option like this… in the core:
It’s probably really easy to add it to the core, like 2 extra lines of code?
Some people (not just me) like this idea.
It’s not pluggable so in order to make it work, it needs to be a core feature (or add a core component).
I don’t know how the core looks here but just an example: