Angular Data Grid Feature Sets & Bundle Size

The grid registers a set of TanStack Table features at construction. Options gate behavior; the feature set gates registration — an API only exists on the table when its feature is registered. Because @tanstack/angular-table is a regular dependency of your app bundle, the feature set you pass is what your bundler ships: with dataGridLiteFeatures the unregistered features are tree-shaken away.

import { Component } from '@angular/core'
import { DataGridComponent, dataGridLiteFeatures } from '@coreui/angular-data-grid'

@Component({
  imports: [DataGridComponent],
  template: `
    <c-data-grid
      [columns]="columns"
      [features]="features"
      [items]="items"
      [pagination]="{ pageSize: 20 }"
      [toolbar]="{ search: true }"
    />
  `
})
export class GridComponent {
  readonly features = dataGridLiteFeatures
  // columns, items ...
}

The features input is read once at table creation — change it together with a component recreation, not on the fly. You can also compose your own set with tableFeatures({...}) from @tanstack/angular-table; the option-coverage check below tells you when a config needs more than the set provides.

What a lite grid can and cannot do

Everything driven by sorting, column filters, the global search and pagination works exactly like the full set — dataGridLiteFeatures keeps the same sort and filter functions. Inputs whose feature is missing from the set throw at construction with the pair spelled out, instead of failing somewhere mid-render:

DATA-GRID: Option "columnPinning" requires feature "columnPinningFeature" in "features".

That covers columnPinning, columnSizing, columnVisibility, columnOrder, rowSelection and filterType: 'select' columns (the faceted value list needs faceting). CSV export and state persistence degrade gracefully: the export follows whatever layout the registered features track, and a state snapshot taken on one feature set restores into a grid running another — absent slices are skipped.

TypeScript keeps the surface honest: the public table property and the template context types carry the grid’s feature set as a type parameter, so a lite table never claims APIs its runtime did not register.