HomeFrontend Development › ClientLibs deep dive

ClientLibs deep dive

Purpose: Categories, dependencies vs embeds, proxying, minification and cache-busting — beyond the Session 7 basics.

Who this page is for

AudienceWhy it matters to you
Frontend engineersBundling reference

Folder properties reference

PropertyEffect
categoriesNames this lib participates in (a lib can serve several)
dependenciesCategories loaded before, as separate files
embedCategories merged into this lib's output
allowProxyServe via /etc.clientlibs proxy (required for /apps libs on publish)
jsProcessor / cssProcessorPer-lib minification config (e.g. min:gcc)
channelsDevice-channel targeting (rare)

dependencies vs embed decision

Questiondependenciesembed
Shared vendor lib used by several bundles?✔ (cache once)✗ (duplicated bytes)
Component CSS into the site bundle?✗ (request per lib)✔ (one file)
Must load before your code executes?✔ ordering guaranteed✔ within one file

Typical shape: phi.dependencies (vendor, rarely changes — great cache hit rate) ← dependency of phi.site (embeds all component libs — changes each release).

Serving & caching

Rules

Quick navigation