Future Features and Ideas (2025+)

[ghiscoding]

• 1. PDF Export, see UI-Grid data export and in code
• 2. possible Backend Service package to support Hasura , see this comment
• 3. Row Detail with portal/teleport (see previous discussion)

  • you are talking about component portaling. in angular via cdk https://material.angular.io/cdk/portal/overview (see article) and react createPortal hook https://react.dev/reference/react-dom/createPortal. in Vue it should be this https://vuejs.org/guide/built-ins/teleport.html

• 4. possibly switch to column hidden property, which we tried in the past via this SlickGrid PR. It could be an issue in ColumnPicker/GridMenu, requires more in depth testing
• 5. 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)
• 6. 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)
• 7. 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 34 below)
• 8. replace custom tooltip with native popover (see discussion native popovers #1709)
• 9. menu auto-positioning by available body space could eventually be replaced by css-anchor-positioning
  • this may take a while since it's still experimental in Safari and isn't yet available in Firefox
• 10. wonder if it's ever possible to use Web Workers to run Export to Excel? In theory, I think it wasn't possible because we need to have access to the dataview and process code like exportWithFormatter but perhaps it's just a matter of sending all of that to the worker? Ask co-pilot for help
• 11. 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
• 12. a possible assumption is that Signal will eventually be JS native and when that happens we'll want to incorporate in here
  • see TC39 proposal-signals
  • will that replace our RxJS implementation? It might be a very long shot if this ever happen, but it might be a possibility
• 13. use --module node20 in the future (comes with TS v5.9)
• 14. to decrease build size, we could use DOM utils from ms-select and drop duplicates from SlickGrid (might need to re-export utils)
• 15. eventually use Angular's built-in integration of Vitest build runner, get rid of AnalogJS, this is currently a new experimental feature in Angular 20
  • see experimental unit testing system
  • see also How to use Angular 20 experimental Vitest support outside of ng test
  • actually I might just drop Analog and Vitest from Angular-Slickgrid, there's not that much benefit to keep unit tests in there when no other framework wrappers has tests (currently it's only the vanilla one and Angular-Slickgrid that have unit tests). Dropping this would allow me to drop Analog+Nx and would also allow bumping TypeScript to latest v5.9+ since only the tests are affected by the TypeScript bump (the build works fine with fixed TS version in package, not sure why Vitest doesn't work well though)
• 16. update TypeScript to latest (currently can't use latest because of Angular, maybe v20 will help)
• 17. should we move row move handler directly into the plugin instead of asking the user to always implement it themselves
• 18. change ms-select lazy load to use resolve() and reject() callbacks (same as Tree Data Lazy Load), but that will require a major version
• 19. remove references to old date picker (flatpickr) docs
• 20. migrate to Rolldown-Vite
• 21. remove any pnpm overrides
• 22. 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
• 23. upgrade to Vitest v4
  • see chore/vitest4-beta11 branch (requires an override to rolldown-vite@latest to be fully migrated)

---

compare Bundle size tools

• packagephobia
• bundlejs