Add JavaScript Grids

[statico]

Added a link to grid libraries organized by features and frameworks.

https://github.com/statico/awesome-javascript-grids#readme

Spreadsheet and data grid components for displaying tabular data on the web, with an interactive explorer and feature comparison companion site.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

• Fully AI-generated pull requests are not accepted.
• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 4 other open pull requests.
  • Add Terraform Compliance #4203 (comment)
  • Add Feature Flags #4167 (comment)
  • Add Company as a Service #4205 (comment)
  • Add CKEditor #4107 (comment)
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
• Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
• Your entry should be added at the bottom of the appropriate category.
• The title of your entry should be title-cased and the URL to your list should end in #readme.
• No blockchain-related lists.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
• Is not AI-generated.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
• It's the result of hard work and the best I could possibly produce.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
• The heading title of your list should be in title case format: # Awesome Name of List.
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.

  These are included in the app view, but not in the Markdown list

• Includes a project logo/illustration whenever possible.
  • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
  • The image should link to the project website or any relevant website.
  • The image should be high-DPI. Set it to a maximum of half the width of the original image.
  • Don't include both a title saying Awesome X and a logo with Awesome X. You can put the header image in a # (Markdown header) or <h1>.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  • Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
  • Should only have one level of nested lists, preferably none.
  • Must not feature Contributing or Footnotes sections.
• Has an appropriate license.

  Dual license - CC0 for prose, MIT for code (separate LICENSE-CODE file)

  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. The casing is up to you.
  • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
  • The section should not appear in the Table of Contents.
• All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
• Has consistent formatting and proper spelling/grammar.
  • The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • The description starts with an uppercase character and ends with a period.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Does not use hard-wrapping.
• Does not include a CI (e.g. GitHub Actions) badge.
  You can still use a CI for linting, but the badge has no value in the readme.
• Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

[statico]

unicorn

[0x11c11e]

Hey,
Two small things while skimming the list:

• Line 80 (SVAR DataGrid): the description is truncated with … and doesn't end with a period: "...keyboard navigation, and special helper for…". Per the PR template, entries need to end with a period; looks like it got cut off mid sentence.
• Line 40 (Functional Data Grid): "This is a library made with React and React-Virtualized..." reads a bit redundant. Could be tightened to something like "Data grid built with React and React-Virtualized for rich tabular displays."

Nice work.

[Nanboy-Ronan]

Two things look unresolved against the template:

• The PR body leaves Non-generated Markdown file in a GitHub repo unchecked and says the list comes from YAML data files. The Awesome guidelines explicitly require a non-generated Markdown file, so this either needs to be changed or called out as something that needs maintainer approval before merge.
• The description in the PR body starts with "A human-curated list of...", which describes the list instead of the project/theme. The entry description in the diff is much better: Spreadsheet and data grid components for displaying tabular data on the web. I would use that style in the body/top description too.

Also, the earlier comment about the truncated SVAR DataGrid description should be addressed before this is ready.

[statico]

@0x11c11e

• Line 80 (SVAR DataGrid): the description is truncated with … and doesn't end with a period: "...keyboard navigation, and special helper for…". Per the PR template, entries need to end with a period; looks like it got cut off mid sentence.

Good catch, fixed.

• Line 40 (Functional Data Grid): "This is a library made with React and React-Virtualized..." reads a bit redundant. Could be tightened to something like "Data grid built with React and React-Virtualized for rich tabular displays."

Much better, fixed.

@Nanboy-Ronan

• The PR body leaves Non-generated Markdown file in a GitHub repo unchecked and says the list comes from YAML data files. The Awesome guidelines explicitly require a non-generated Markdown file, so this either needs to be changed or called out as something that needs maintainer approval before merge.

Fair enough. The README is no longer auto-generated.

• The description in the PR body starts with "A human-curated list of...", which describes the list instead of the project/theme. The entry description in the diff is much better: Spreadsheet and data grid components for displaying tabular data on the web. I would use that style in the body/top description too.

Good call, fixed.

Also, the earlier comment about the truncated SVAR DataGrid description should be addressed before this is ready.

Done.

[hwajongpark]

Mechanically clean; two content points:

1. The list leans exhaustive rather than curated (~75 entries), including AngularJS/jQuery-era projects and many overlapping single-vendor SKUs (Kendo for Angular/Vue/Grid/Spreadsheet/KendoReact; Sencha Ext JS/ExtAngular/ExtReact; Jspreadsheet CE/Pro). Worth trimming toward "the best, not everything."

2. Minor: the entry says "components" but the list catalogs libraries/products (the section is literally ## Libraries), and "ag-Grid" is stale, since the vendor rebranded to "AG Grid."

[atamano]

Adding to the curation points already raised:

• Sencha Ext JS, ExtAngular, ExtReact, jQWidgets, and Ignite UI are full UI suites, while this list is specifically about grids. Their entries should link directly to the relevant grid component or grid documentation rather than the suite landing page.
• Some descriptions need to be rewritten as self-contained, objective descriptions. DataTables says it "adds all of these advanced features to any HTML table", but "these" has no antecedent in the list. Jspreadsheet CE uses the promotional phrase "amazing web-based online interactive tables" rather than describing its functionality objectively.