npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ag-grid-boost

v17.0.0

Published

Advanced Data Grid / Data Table supporting Javascript / React / AngularJS / Web Components

Downloads

198

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

tnthubtnthub

Keywords

web-componentsgriddatatableangularangular-componentreactreact-componentangularjsreactjs

Readme

ag-Grid

CDNJS npm npm

"ag" stands for AGnostic

Install with Bower

$ bower install ag-grid

Install with Npm

$ npm install ag-grid

See www.ag-grid.com for overview and documentation.

Frameworks Supported

Framework specific Getting Started guides:

Angular 1 | Angular 2 | Aurelia | Javascript | React | TypeScript | VueJS | Web Components

Building

To build:

  • npm install
  • npm install gulp -g
  • bower install
  • gulp or gulp release

Default gulp task is for development. It includes source maps, does not include minification, and starts a watch.

'release' gulp task does minification and no source maps. This is for releasing.

Folder Structure

The new build has the following structure:

  • \src -> contains source files (TypeScript and CSS), don't touch these!
  • \dist -> contains distribution files
  • \dist\ag-grid.js and \dist\ag-grid.min.js -> use these if not using a package manager and put ag-Grid on the global scope. The new JavaScript distribution files contain the CSS for the grid, no need to reference separately.
  • \dist\styles -> contains CSS files, used if doing your own bundling.
  • \dist\lib -> contains compiles JavaScript files in CommonJS format.
  • \main.js -> CommonJS root file, reference this file if importing project via CommonJS.
  • \main.d.ts -> CommonJS root definition file.

Asking Questions

Please do not use GitHub issues to ask questions. Ask questions on the website forum.

Contributing

ag-Grid is not looking for contributors. It is not intended to be developed by an online community. However suggestion on change and raising bugs are appreciated.

If you are doing a Pull Request:

  • Make your code changes in src/ files only, don't update dist files
  • Discard all changes to dist/
  • Create Pull Request

For large changes:

  • Make your doc changes in project ag-grid-docs, a feature is not complete unless it's documented!
  • Do manual end to end testing off all examples in documentation

PR's on new features are not generally accepted.

PR's on small bug fixes are generally accepted.

If a PR for a large request is submitted, the typical action is the author will take influence from the code to implement the feature, either in ag-grid or ag-grid-enterprise.