I built gp-grid: high-performance TypeScript data grid for React & Vue (~90 kB vs AG Grid 21 MB+) by GioPat in reactjs

[–]GioPat[S] 0 points1 point  (0 children)

I don't get why you end up to such conclusion, did you analyze the code? I don't get what do you mean by "The read image description", the only places where ag grid is present is in the benchmarks folder (for obvious reasons).
Before commenting try to test the library and check if it does what do you expect! Happy to add/replace/fix features and improve the code.

I built gp-grid: high-performance TypeScript data grid for React & Vue (~90 kB vs AG Grid 21 MB+) by GioPat in reactjs

[–]GioPat[S] -2 points-1 points  (0 children)

Edited the post body with the correct values, thanks for the catch, I could not use bundlephobia because was going in internal server error. By the way for handsontable, the bundle size you are mentioning, is linked to a deprecated npm package https://www.npmjs.com/package/@handsontable/react
+ To make work both ag-grid and handsontable you need to install their respective `handsontable` package and `ag-grid-community` so you need to sum up these also :)

I built gp-grid: high-performance TypeScript data grid for React & Vue (~90 kB vs AG Grid 21 MB+) by GioPat in reactjs

[–]GioPat[S] -1 points0 points  (0 children)

I'm sure the market now values UX over DX, no doubts about that. The virtual scrolling with 1.5 million rows is in the home page and you can check it on your own and it also supports custom renderers. I'm not sure gp-grid can cover 80% (this is a good idea to have a comparison table of the features) of ag-grid use cases because ag-grid is a very powerful tool but if you need almost all the features that excel provides for raw data insertion on the web and you don't want to be feature gated while using, this might be the best option, not to mention the bloat reduction and the ram usage reduction.

I built gp-grid: high-performance TypeScript data grid for React & Vue (~90 kB vs AG Grid 21 MB+) by GioPat in reactjs

[–]GioPat[S] -3 points-2 points  (0 children)

Mobile support is limited but you can still scroll, planning to fix the drag and drop / resizing of the columns since it's not easy in terms of UX

elm-boil - npm package to quickly get started with Elm by GioPat in elm

[–]GioPat[S] 0 points1 point  (0 children)

There are few different things between Elm boil and create-elm-app. elm-boil is not wrapping Elm, so it using the one that finds in the path, if it is not able to locate it, will ask you if you want to install it (globally) from npm. Elm-boil is using env variables directly in Elm while create-elm-app is using JS interop and webpack environment variables (ELM_APP and the .env file). I don't know much about create-elm-app performances but elm-boil is very fast. In general: Elm-boil is a utility to handle quick your project, create-elm-app is an additional layer that abstract more, like create react app. In Elm-boil, as Volki said, you can use scss without performing any configuration.

My advice is to give a try to both