obsidian flicker
On a recent patch upgrade (9.22.1 to 9.22.4) the support for "pack" extensions has been suddenly removed.
I realise they were not officially supported, but it fit snugly on our use-case so we used it to group some stuff and delivery some features.
Is there any plan to reintroduce them in some form? do we have to migrate to bundle extensions (which are equally undocumented)?
shouldn't a structural change like that require more discussion or at least a minor version bump?
grave scaffold
@hollow siren Introduced packs without implementing them fully so we ended up with a half implemented half not working extension type. That's why I removed it.
I don't think we will ever introduce them back as they didn't really add much to the table. And I didn't anticipate to someone using them as even we had trouble figuring out what packs where doing.
obsidian flicker
we've been using them for about a year, never had particular problems
i haven't looked much into how bundles are organised yet, but i quite like how we organised the repos/workspaces to build "feature packs" (as we call internally a bunch of extensions shipped together)
it might also be that we haven't used them in the same way as you imaged them tho
are you completely closed to the idea of having/reintroducing that type of extensions? or could we share our experience and see if it's a feature worth keeping?
opaque moss
bundle and pack both allow you to ship multiple extension in one package but bundles have the advantage of sharing the dependencies between the bundled extensions (resulting in smaller sizes)
obsidian flicker
yes, i imagine. i'll have to try them out in any case. the bundle does not allow me to ship extensions either singularly or packaged up with other. but it's a limited use case that i think i could work around of
i quite like my workspace-powered repos that publishes various npm modules, one of which has the responsibility of bringing all the extensions together into a coherent feature. but that's a matter of pride and i'll get over it
dependency wise we haven't yet encountered a case were we have many duplicated ones, often are small extensions that leverages the dependencies already provided by the platform