(done) 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: end of February, 2026

---

• 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
• 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
  • arggg another Salesforce exception!!! it doesn't work in that environment, so I need to add a fallback
    • ref PR refactor: add CompositeEditor domElementType fallback for Salesforce #2350
• 4. can we use alien-signals instead of our built-in Binding Helper / Binding Service / collectionObserver & propertyObserver?
  • see PR chore: use Signals in Custom Pagination instead of custom binding helper #2128
  • after trying a few things with copilot using Proxy and/or Signals, it seems that my current approach is still the best if we stick with plain arrays. It might have worked if I switch arrays to Proxies or Signals, but that would be a breaking changes that I'm not sure I want to introduce on collectionAsync in Filter/Editors (maybe in the future but not for now, so let's cancel this change).
• 5. use --module node20 or target ES2023 in the future (comes with TS v5.9)
  • I tried targeting ES2023 instead of ES2021 and it's producing slightly larger build size (similar to what I've observed last year with ES2022), so for that reason I think that staying with ES2021 produces the best results (aka smaller build sizes)
• 6. change ms-select lazy load to use resolve() and reject() callbacks (same as Tree Data Lazy Load), but that will require a major version
  • ref PR chore(deps): update multiple-select-vanilla to v5.0 #2357
  • also release a major version for Excel-Builder-Vanilla, also update gzip size badge by using BundleJS
• 7. remove references to old date picker (flatpickr) docs
• 8. 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
  • ref PR chore(deps): update remove-glob/native-copyfiles to new major #2336
• 9. remove tinyglobby usage in compress.mjs via Node 22.17 and import { globSync } from 'node:fs';
• 10. 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
• 11. remove Cell/Row Selection Models and keep only SlickHybridSelectionModel
  • ref PR feat!: drop Cell/Row Selection Models & keep only HybridSelectionModel #2330
  • might be a problem with master/detail row selection (single row selection) (fixed by PR fix: allow single row selection via click without checkbox column #2311)
  • should we keep enableHybridSelection grid option or should we choose something else? Nope, migrated to simpler enableSelection
• 12. rename Hybrid Selection rowSelectionOptions to selectionOptions
• 13. make Row Detail optional in all framework wrappers (next major and update docs to mention separate install)
  • ref PR feat!: make Row Detail plugin as optional in all framework wrappers #2291
  • need to add it to each Migration Guides
  • need to publish to npm once for OIDC (use https://github.com/azu/setup-npm-trusted-publish)
• 14. Angular:
  • upgrade to Angular 21 (ref PR feat!: upgrade to Angular 21, fixes #2335 #2338)
  • Vitest is now the default unit testing setup in Angular 21 🚀 so we could get rid of AnalogJS entirely
    • see also How to use Angular 20 experimental Vitest support outside of ng test
      • this is the setup, even if experimental, that worked (the built-in one failed on me)
      • ref PR chore(deps): drop AnalogJS and use an experimental Vitest setup #2344
  • 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
    • update docs for "Getting Started" with latest ngx-translate setup
    • update docs for Migration Guide v10
  • migrate all Angular examples to Standalone Components
    • ref PR feat(angular)!: migrate Angular-Slickgrid to Standalone Component #2339
    • 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
  • use oxlint jsPlugins with angular-eslint (ref PR chore: try oxlint jsPlugins with angular-eslint #2223)
  • can we go zoneless by removing zone.js - ref PR feat(angular)!: migrate Angular-Slickgrid to Zoneless #2341
  • run all Angular migrations: https://angular.dev/reference/migrations
• 15. React:
  • Deprecated In React 19, forwardRef just pass ref as a prop since forwardRef will be deprecated in a future React release.
• 16. Vue
  • rename v-model:data to v-model:dataset so that it matches all other wrappers
    • ref PR feat(vue)!: rename v-model:data to v-model:dataset #2298
• 17. remove all @deprecated code
• 18. drop most TypeScript enum and replace them with type (e.g. FieldType)
• 19. rename all double type filenames, e.g. caseType.type.ts should just be case.type.ts
  • maybe also rename filenames like operatorString.type.js
• 20. write Migration Guide 10.x
• 21. maybe we could auto-enable external resources since user already loaded them (i.e. ExcelExportService => enableExcelExport)
  • ref PR feat: auto-enabled external resources with their associated flags #2362
• 22. 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()
  • tested in Salesforce LWC and it doesn't work, it might work with LWS but we're not using it yet
• 23. test in Salesforce
• 24. simplify single Locale in all framework wrappers demos
  • also add single Locale to React/Vue demos
• 25. deprecate ExtensionName and provide string template type until removal in next major v11
  • ref PR chore: deprecate ExtensionName enum to be replaced by string type #2349
• 26. try to use spreading of global grid options in each framework instead of duplicating them entirely (eventNamingStyle will be different in each framework), ref PR chore: spread GlobalGridOptions from common to all frameworks #2360
• 27. review all pnpm overrides and probably delete a few
• 28. create a copy of master branch as version9 branch and also do the same for all frameworks demo repos
• 29. duplicate/similar code can be found in changeColumnsArrangement() and in each framework wrappers loadColumnPresetsWhenDatasetInitialized(), let's try to merge them in the future
  • ref PR refactor(presets): merge duplicate column preset loading logic #2364

After release

• merge next branch to master branch