Patternslib/Patterns

Patternslib distribution / what should be included in the bundle

Closed this issue · 1 comments

thet commented

At the peer session with @cornae we discussed the situation with the default patterns which go in a bundle with each new Patternslib release.

Some important patterns are not included, e.g. pat-upload, pat-content-mirror or pat-tiptap.
Even though we have lazy loading of external dependencies, adding more patterns will make dependency management harder.
To develop or build Patternslib a lot of external 3rd party packages have to be downloaded and maintained. Besides of a big download size this can give problems when managing dependencies, e.g. a library gets outdated and depends on 3rd party libraries which are not supported by Patternslib anymore - e.g. a old version of jQuery. We cannot simply remove that dependency from core patternslib then without a proper deprecation process.
On the other hand, integrating more and more patterns also has some advantages, like no need to manage and update the external Patternslib dependency in external patterns.
However, I'd even prefer to peel out the core Patternslib code in a seperate project, so that not all of the 3rd party libraries have to be downloaded if we just need the patterns registry.

I'd suggest to create a Patternslib distribution which includes all Patterns which we currently want to ship with a download zip file on patternslib.com.

/cc @pilz