These are chat archives for bem/talk
so "economy" after deprecating noDeps not so significant
you should deprecate it not for economy, but for not letting consumers use your code in bad way
noDepsome block it's a signal to block's maintainer to split it into smaller parts and not include them all
i-bem__dom_init_autoto not force consumers use noDeps, and that's all
html- is this means, that this deps would be for
depsfile in block directory can define dependencies for other blocks (if I include properties of those blocks in deps file)?
mustDeps) for another block
b2 mustDeps b1
it's not actually about broke incapsulation — it's about nuance in form of describing order deps
noDepsmay be implemented by filtering blocks before/after dependencies resolution - so plugin it is.
noDeps(in case if you need it)
noDepsusage clear, that it always written in one place (for us it written in page deps) - so it can be moved to build configuration.
noDeps- then it will be used by consumers
b-pagefrom lower level.
pageblock on bundle level
i-bem__dom_init_auto? cause if not, I'm still miss of point