1import{a}from"./chunk-DFWWWU2G.js";import{a as o}from"./chunk-FZ6JLVMW.js";import{a as i}from"./chunk-UMOUURVK.js";import{a as g,b as E}from"./chunk-YY4YCK5F.js";import"./chunk-RMZUX6ZM.js";import"./chunk-B7EPENHE.js";import{a as r}from"./chunk-KBXFIZT3.js";import"./chunk-T7SA5VQS.js";import"./chunk-NVNIRCRG.js";import"./chunk-WRCSE6XA.js";import"./chunk-VJOG7BHU.js";import"./chunk-RIE32WQ5.js";import"./chunk-D7UVY4ND.js";import"./chunk-Y65KIHR3.js";import"./chunk-HP5QCM5I.js";import"./chunk-T4UYT6YZ.js";import"./chunk-DPXL5ZHC.js";import{Jb as h,Mb as m,_ as d,ob as c}from"./chunk-TUWXKLON.js";import"./chunk-Z4C26HH6.js";import{a as l,b as p}from"./chunk-OSQMNGTH.js";var f={"installer-interactive":i,"installer-non-interactive":a,"installer-resolved-dependencies":o},u=class s{exampleRegistry=d(g);exampleGroups=r;installerLibrary={title:"ng-hub-ui",description:"The ng-hub-ui family installer: one `ng add` command that asks which libraries you want, resolves the packages each of them needs, and writes them into your manifest.",overview:{text:"`ng-hub-ui` is the umbrella package of the family, and the only one that ships no components. What it ships is an `ng add` schematic: it offers the 25 catalogued libraries in a multi-select prompt, or takes the identifiers straight from a `--libraries` flag, and resolves each selection into the npm packages it actually needs \u2014 including the peers a library depends on and the one external package (`sortablejs`) that is not ours. The resolved list is written into `dependencies` at the workspace root, never overwriting a key that is already there, and then handed to whichever package manager the Angular CLI detects. Its scope stops at dependency wiring: it does not touch `angular.json`, register providers, import components or add stylesheet entries.",highlights:[{icon:"fa-solid fa-terminal",title:"DOCS.INSTALLER.FEATURE.ONE_COMMAND.TITLE",description:"DOCS.INSTALLER.FEATURE.ONE_COMMAND.HIGHLIGHT"},{icon:"fa-solid fa-code",title:"DOCS.INSTALLER.FEATURE.SCRIPTABLE.TITLE",description:"DOCS.INSTALLER.FEATURE.SCRIPTABLE.HIGHLIGHT"},{icon:"fa-solid fa-diagram-project",title:"DOCS.INSTALLER.FEATURE.RESOLVED_DEPENDENCIES.TITLE",description:"DOCS.INSTALLER.FEATURE.RESOLVED_DEPENDENCIES.HIGHLIGHT"}],changelog:[{version:"0.2.3",date:"2026-09-28",changes:[{type:"changed",description:"The family list in both READMEs names `ng-hub-ui-spreadsheet`, and the READMEs now carry a commercial-support section. Documentation only: no code, types or styles change."}]},{version:"0.2.2",date:"2026-09-16",changes:[{type:"changed",description:"Repository, issue and README links follow the move to the hub-env organization. Issues for every Hub UI package are now gathered in hub-env/hub-ui, and the repository and bugs fields of the manifest point at the new addresses. No code, types or styles change."}]},{version:"0.2.1",date:"2026-09-08",changes:[{type:"fixed",description:"Four documents said the installer has no page on the documentation site. This is that page: both READMEs and `FUNCTIONALITIES.md` link to it instead of denying it."},{type:"changed",description:"The manifest `homepage` points at this page rather than at the family root \u2014 it is the link a registry shows beside the package, and every other library in the family already points at its own documentation. Metadata only: no code, no schematic behaviour, no catalogue change."}]},{version:"0.2.0",date:"2026-09-06",changes:[{type:"fixed",description:"Every one of the 25 catalogue ranges now floors at or above the highest peer the family declares on it. `ng-hub-ui-forms` had reached 22.32.0 peering on `ng-hub-ui-utils >=22.12.0` while the catalogue still offered `utils ^22.8.1`, so `ng add ng-hub-ui --libraries=forms` wrote a pair npm cannot satisfy \u2014 invisible on a fresh unpinned install, an `ERESOLVE` anywhere resolution was already fixed."},{type:"fixed",description:"Both READMEs denied a library the installer has offered since 0.1.6: they said `ng-hub-ui-action-sheet` was not on npm, in five separate places, while the catalogue had carried it all along."},{type:"changed",description:"The Angular peer range is `>=18.0.0`, up from `>=17.3.0`. Nothing in the catalogue targets Angular 17, so the old floor let `ng add ng-hub-ui` run, write the manifest and only then fail to resolve. See `BREAKING_CHANGES.md`."},{type:"added",description:"The schematic has a tracked spec again. The only test over `ng add` lived beside the compiled output where `.gitignore` excludes it, so it left the repository the moment it was written; run today it reported three failures it had been reporting for months."}]},{version:"0.1.7",date:"2026-09-01",changes:[{type:"changed",description:"The manifest `homepage` points at the localized site root rather than the redirect above it, so a reader arriving from npm lands one hop earlier."}]},{version:"0.1.6",date:"2026-08-30",changes:[{type:"added",description:"`action-sheet` joins the catalogue and the prompt: `ng-hub-ui-action-sheet` reached the registry with 22.0.0, and it needs no co-installs."}]}]},functionalities:[],api:{inputs:[],outputs:[],templates:[],cssVariables:[]},styling:[]};ngOnInit(){this.registerExamples(),this.populateFunctionalities()}registerExamples(){[{id:"installer-interactive",title:"DOCS.INSTALLER.EXAMPLE.INTERACTIVE.TITLE",componentName:"InteractiveInstallerExampleC
1omponent",files:["interactive-installer-example.component.ts"],sourceCode:i.sourceCode,loader:()=>import("./chunk-U53JED7E.js").then(e=>e.InteractiveInstallerExampleComponent)},{id:"installer-non-interactive",title:"DOCS.INSTALLER.EXAMPLE.NON_INTERACTIVE.TITLE",componentName:"NonInteractiveInstallerExampleComponent",files:["non-interactive-installer-example.component.ts"],sourceCode:a.sourceCode,loader:()=>import("./chunk-E2ZKQJRR.js").then(e=>e.NonInteractiveInstallerExampleComponent)},{id:"installer-resolved-dependencies",title:"DOCS.INSTALLER.EXAMPLE.RESOLVED_DEPENDENCIES.TITLE",componentName:"ResolvedDependenciesInstallerExampleComponent",files:["resolved-dependencies-installer-example.component.ts"],sourceCode:o.sourceCode,loader:()=>import("./chunk-KQMKJKEV.js").then(e=>e.ResolvedDependenciesInstallerExampleComponent)}].forEach(e=>{this.exampleRegistry.register(p(l({},e),{packagePath:"installer"}))})}populateFunctionalities(){this.installerLibrary.functionalities=r.map(t=>({title:t.title,description:t.description,examples:t.exampleIds.map(e=>this.createExample(e)).filter(e=>e!==null)}))}createExample(t){let e=this.exampleRegistry.get(t),n=f[t];return!e||!n?null:{title:e.title,description:`DOCS.INSTALLER.EXAMPLE.${this.descriptionKeySegment(t)}.DESCRIPTION`,import:"",template:"",component:"",previewComponent:n}}descriptionKeySegment(t){return t.replace(/^installer-/,"").replace(/-/g,"_").toUpperCase()}static \u0275fac=function(e){return new(e||s)};static \u0275cmp=c({type:s,selectors:[["app-installer"]],decls:1,vars:4,consts:[[3,"library","package","install","exampleGroups"]],template:function(e,n){e&1&&m(0,"app-library-page",0),e&2&&h("library",n.installerLibrary)("package","installer")("install","ng add ng-hub-ui")("exampleGroups",n.exampleGroups)},dependencies:[E],encapsulation:2})};export{u as InstallerComponent};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.