1 min readNov 2, 2018
High-cost configuration and customization features should be provided separately from library “core”. It can be either tree-shakeable modules or separated files. Just import some additional feature, link it with core and be happy
Half year ago I published a post with 3 “must-have” patterns for libraries. It was written for another point but these patterns really help to write lightweight libraries with opportunity to extend ’em easily.
