Roadmap to 10.0 (2026-Q1)

[ghiscoding]

next major version

Listing some of the expected ideas to be executed for next major, I'm not sure about some of them so we'll see how it goes. But even then, for the most part the list below should be pretty close to what is expected for the next major.

Expected date: around 2026 end of Q1

---

• 1. possibly switch to column hidden property, which we tried in the past via this SlickGrid PR. It will be an issue in ColumnPicker/GridMenu, requires more in depth testing (reserve it for a major version)
  • ref PR feat!: switch to column hidden property and always keep all columns #2281
  • also need to update docs related to the breaking change
• 2. rewrite Grid Menu logic to use CSS flexbox instead of calc(100% - 18px)
  • ref PR refactor!: rewrite Grid Menu using CSS flexbox instead of width and calc() #2282
• 3. rewrite Composite Editor with native <dialog> DOM element
  • ref PR feat!: migrate SlickCompositeEditor modal from <div> to <dialog> #2283
• 4. can we use alien-signals instead of our built-in Binding Helper / Binding Service?
  • might be better to wait for next major
  • see PR chore: use Signals in Custom Pagination instead of custom binding helper #2128
• 5. use --module node20 in the future (comes with TS v5.9)
• 6. to decrease build size, we could use DOM utils from ms-select and drop duplicates from SlickGrid (might need to re-export DOM utils)
• 7. change ms-select lazy load to use resolve() and reject() callbacks (same as Tree Data Lazy Load), but that will require a major version
• 8. remove references to old date picker (flatpickr) docs
• 9. bump Node requirement in root (local Dev only) to Node 24 so that we can get rid of tinyglobby in my other dev libs (remove-glob, native-copyfiles) with next major versions
• 10. remove tinyglobby usage in compress.mjs via Node 22.17 and import { globSync } from 'node:fs';
• 11. update TypeScript to latest (currently can't use latest because of Angular, wait for our next major bumping Angular to v21)
  • remove baseUrl from all tsconfig
• 12. Angular:
  • upgrade to Angular 21
  • run all Angular migrations: https://angular.dev/reference/migrations
  • Vitest is now the default unit testing setup in Angular 21 🚀 so we could get rid of AnalogJS entirely
    • see experimental unit testing system
    • see also How to use Angular 20 experimental Vitest support outside of ng test
    • see also https://blog.ninja-squad.com/2025/11/20/what-is-new-angular-21.0
  • remove any pnpm overrides and bump to Vite 7 in Angular-Slickgrid
  • upgrade ngx-bootstrap and ngx-translate to new major versions with breaking changes in next Angular-Slickgrid major
    • also need to update docs for "Getting Started" with latest ngx-translate setup
  • migrate all Angular examples to Standalone Components
    • migrate Angular-Slickgrid component/module on the next major only, to avoid breaking changes (see below)
    • also need to rollback commit 429aae1 to be fully Standalone in next major
    • we might also be able to switch @input to Signals based
  • use oxlint jsPlugins with angular-eslint (ref PR chore: try oxlint jsPlugins with angular-eslint #2223)
  • can we go zoneless (by removing zone.js)?
• 13. remove Cell/Row Selection Models and keep only SlickHybridSelectionModel
• 14. make Row Detail optional in all framework wrappers (next major and update docs to mention separate install)
• 15. should we change Formatter last argument (grid) to (gridOption), so that it could be more Web Worker friendly for future Excel Export?
  • or instead of 5 arguments, would it be better to regroup them all into a single object? That is a huge breaking change though...
• 16. React:
  • Deprecated In React 19, forwardRef is no longer necessary. Pass ref as a prop instead. forwardRef will be deprecated in a future release.
• 17. remove all @deprecated code (like FieldType and many Enums)
• 18. duplicate/similar code can be found in changeColumnsArrangement() and in each framework wrappers loadColumnPresetsWhenDatasetInitialized(), let's try to merge them in the future
• 19. provide an ESM only PR to un-flatten-tree repo, or fork the project as a last resource (only if future PR of ESM isn't accepted)
• 20. remove internal deep copy of GridOption and allow user to update any options by pointer or reference
  • see this Angular-Slickgrid issue for more context
  • it might not be possible to make it like a pointer ref (and reactive) but we could use onSetOptions to resync (but might fall into infinite loop though)
• 21. would it work with Vite 8? I know Aurelia is blocked at the moment
• 22. write Migration Guide
• 23. could we try to move some (e.g.: RowDetail, RxJS), or all, extensions as optional and maybe do something similar to what I've done in Lerna-Lite code which is to use await import(plugin). I'm guessing that ViteJS is potentially doing similar with SASS which doesn't work until you npm install SASS
  • could we auto-enable certain flags when their associated external resources are loaded? (i.e. ExcelExportService => enableExcelExport) (not sure yet since this might be the inverse of step above)
• 24. it looks like document.createDocumentFragment() might be compatible with Salesforce LWC (instead of new DocumentFragment()), need to test in Salesforce, if it does then get rid of createDocumentFragmentOrElement()

---

Angular Standalone Components

// angular-slickgrid.component.ts
// ...
+ import { NgTemplateOutlet } from '@angular/common';

@Component({
  selector: 'angular-slickgrid',
  templateUrl: './angular-slickgrid.component.html',
  providers: [
    // make everything transient (non-singleton)
    AngularUtilService,
    TranslaterService,
  ],
-  standalone: false,
+  imports: [NgTemplateOutlet],
})

// angular-slickgrid.module.ts
// ...
@NgModule({
-  imports: [CommonModule, TranslateModule],
-  declarations: [AngularSlickgridComponent],
+  imports: [CommonModule, TranslateModule, AngularSlickgridComponent],
  exports: [AngularSlickgridComponent],
})

- import { AngularSlickgridModule } from 'angular-slickgrid';
+ import { AngularSlickgridComponent } from 'angular-slickgrid';

@Component({
  templateUrl: './example01.component.html',
-  imports: [AngularSlickgridModule],
+  imports: [AngularSlickgridComponent],
})

[ghiscoding]

@zewa666 BTW which Angular version are you on currently? I'm starting to work on some item for my next major (first item at the moment) and I'm planning to switch to Angular 21 for my v10.0 mostly because Vitest is now the official new default test framework, woohoo, in Angular and I want to get rid of Analog (too many deps and too many Nx security issues that come out recently, so if I can get rid of Analog and I'll be super happy)...

So anyway, I was asking out of curiosity since I won't release until end of Q1 next year anyway (end of March) to coincide with NodeJS (end of April though). I think one major a year is good on my end.

I'm actually also already planning v11.0 as well (mostly in my head), since I'll postpone CSS Anchor Position for v11.0, Firefox is finally working on adding it and they are the last browser which is still missing the feature, they're at 76% done on their nightly version (see https://wpt.fyi/interop-2025) so it's coming but better wait a year and so planning it for v11.0

[zewa666]

its a tough situation so we've fallen back quite a few versions on v18 now. got a sprint planned for end of january/feb to update all deps and also the backend. while doing so I'll bump all the way to v21

[ghiscoding]

ah yeah no worries, I also personally find that Angular with 2 majors a year is a little over the top. It's hard to keep up with them especially when other big players like React is more like a new major every 4-5 years 😆

So with that in mind, it looks like you're not using v9 yet then!?

[zewa666]

true, only for demo projects so far. but definitely looking forward to it. there's a lot of customizations we've done so upgrade is a bit of a pain and takes time