Since 2025.2, some JS API broke. For a lot of them, the only guidance is Recompile code usages.
What does that actually mean? Can I still keep my plugin’s minimum version lower than 2025.2? Do I have to recompile it without any change (this generates verification errors)?
More generally, how are we supposed to handle this situation if we support minimum versions lower than 2025.2?
We usually recommend branching the plugin in such situations, having a version for older API with bugfixes and the modern one with new features added. It is proven to be one of the most sustaintable ways to maintain a plugin
Could you please post the problems you are facing with? It is rather hard to answer you without concrete examples.
The thing is I don’t want to deprecate the features for older IDE versions that do support perfectly well what my plugin is doing.
And I would prefer avoiding branching my plugin because of the maintenance hassle, the duplication, and the breaking mindset of version management (such practice isn’t semver-friendly), only for a small breakage in a JS variable.
My problem is the following: some JS variables I use (JSStubElementTypes.XML_ATTRIBUTE and some others) have had their types changed in 2025.2, though the new one is still 100% compatible with my use of it in my code.
I think it’s possible to branch the plugin compilation while keeping a mostly common code source, do you have examples for this?
No, we use branching actively and do not worry about delivering features to old IDEs