plugins: optimize is not installed

[Arexils]

I'm trying to use the plugin that build-in, but I'm getting an error.

command: mkdocs serve

ERROR   -  Config value 'plugins': The "optimize" plugin is not installed

Aborted with 1 configuration errors!

my snippet code

plugins:
  - optimize:
      enabled: !ENV [CI, false]
  - minify
  - search

my dependencies in poetry:

mkdocs = "^1.5.2"
mkdocs-material = {extras = ["imaging"], version = "^9.3.1"}
mkdocs-minify-plugin = "^0.7.1"
pymdown-extensions = "^10.3"

https://squidfunk.github.io/mkdocs-material/plugins/optimize/#config.enabled

[alexvoss]

I think what is going on is that optimize is part of the insiders edition and you are using the public version.

[Arexils]

https://squidfunk.github.io/mkdocs-material/insiders/#:~:text=When%20the%20funding%20goal%20is%20hit%2C%20the%20features%20are%20released%20for%20general%20availability.

So I misunderstood that.

[astromatt]

I was fighting to make optimize work for some time. A small information, that plugin is a part of "insiders edition" would help.

[squidfunk]

I need to think about this a little before we settline on a solution. Thanks for providing a working solution and for all you work and time you dedicate to help users on our issue tracker. You rock! 🚀

[astromatt]

IMHO I would go with a solution similar to the one presented above.

In Open Source version of material theme put a list of plugin names from insiders edition. If mkdocs loader would hit "no such plugin" condition, a simple hook should check if this plugin name is on the list, and then just say: "This plugin is not currently installed, but it is in insiders edition. You can learn more here: ..." or something similar.

I think this is more future proof than empty plugin wrapper.

[squidfunk]

Thanks for your input! Themes cannot register auto-mounted hooks or plugins. Unfortunately, it is not that simple.

[alexvoss]

If I can add my 2p: the initial problem is that people do not realize that a feature is part of Insiders. I had a look at the way that Insiders features are labelled in the documentation and for those who are generally aware of the difference between public and Insiders the labeling (beating heart and version indicator that shows the insiders version only) should be enough. The issue, I would guess, is that new users are not sufficiently aware of the distinction. Those of us who just sometimes forget will realize soon enough.

I think we are missing the chance to mention it in the Installation section of the Getting Started page. The front door problem (a lot of people do not use the hierarchical navigation but jump into the documentation from a web search or link) means this will not solve the issue for everyone but adding a note about the different versions in this place should help somewhat and also advertises Insiders at an important point.

[squidfunk]

Ack! We should add this to the requirements of our latest IA considerations.