|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Awesome React Components||37,045||25 days ago||2||cc0-1.0|
|Curated List of React Components & Libraries.|
|📗 SheetJS Spreadsheet Data Toolkit -- New home https://git.sheetjs.com/SheetJS/sheetjs|
|Table||22,560||1,770||1,417||a day ago||217||May 16, 2022||173||mit||TypeScript|
|🤖 Headless UI for building powerful tables & datagrids for TS/JS - React-Table, Vue-Table, Solid-Table, Svelte-Table|
|Blueprint||20,084||1,039||408||2 hours ago||271||July 28, 2023||679||apache-2.0||TypeScript|
|A React-based UI toolkit for the web|
|Ag Grid||10,861||323||505||3 hours ago||76||July 28, 2023||70||other||TypeScript|
|X Render||6,371||1||49||11 days ago||485||July 13, 2023||18||TypeScript|
|🚴♀️ 阿里 - 很易用的中后台「表单 / 表格 / 图表」解决方案|
|Excel-like data grid (table) component for React|
|Empower Your Data with the best React Data Grid there is|
|Datatable for React based on material-ui's table with additional features|
Blueprint is a React-based UI toolkit for the web.
It is optimized for building complex, data-dense web interfaces for desktop applications which run in modern browsers. This is not a mobile-first UI toolkit.
Blueprint's change log and migration guides for major versions live on the repo's Github wiki.
This repository contains multiple projects in the
packages/ directory that fall into 3 categories:
These are the component libraries we publish to NPM.
These are hosted on GitHub Pages as static web applications:
docs-app– Documentation site at blueprintjs.com/docs
landing-app– Landing page at blueprintjs.com
These are used as development playground environments:
demo-app– demo page that shows many components all on the same page in light and dark themes
table-dev-app– demo page that supports manual testing of all table features
These packages define development dependencies and contain build configuration. They adhere to the standard NPM package layout, which allows us to keep clear API boundaries for build configuration and isolate groups of
devDependencies. They are published to NPM in order to allow other Blueprint-related projects to use this infrastructure outside this monorepo.
@blueprintjs/eslint-config, not directly).
Lerna manages inter-package dependencies in this monorepo.
Builds are orchestrated via
lerna run and NPM scripts.
Prerequisites: Node.js v18+ (see version specified in
.nvmrc), Yarn v1.22 (see version specified in
First, ensure you have
nvm (Node Version Manager) installed.
After cloning this repo, run:
nvm useto use the supported Node version for Blueprint development.
corepack enableto activate Yarn as the Node package manager.
yarnto install all dependencies for the monorepo.
npm install -g windows-build-toolsto install build tools globally
bashis your configured script-shell by running:
npm config set script-shell "C:\\Program Files\\git\\bin\\bash.exe"
yarn verifyto ensure you have all the build tooling working properly.
If you were previously in a working state and have just pulled new code from
yarnat the root.
yarn compileto get the latest built versions of the library packages in this repo.
yarn verifysince it doesn't build the application packages (
landing-app, etc.) or run tests
There are a few ways to run development scripts, here they are listed from simplest to more advanced usage:
yarn devfrom the root directory to watch changes across all packages and run the docs application with webpack-dev-server.
cd packages/core && yarn dev
cd packages/icons && yarn dev
cd packages/docs-app && yarn dev
Much of Blueprint's documentation lives inside source code as JSDoc comments in
.tsx files and KSS markup in
files. This documentation is extracted and converted into static JSON data using
If you are updating documentation sources (not the docs UI code which lives in
packages/docs-app or the docs theme
packages/docs-theme), you'll need to run
yarn compile from
packages/docs-data to see changes reflected in the
application. For simplicity, an alias script
yarn docs-data exists in the root to minimize directory hopping.
The One-time setup and Incorporating upstream changes steps should produce the generated source code in this repo used to build the icons documentation. This is sufficient for most development workflows.
If you are updating icons or adding new ones, you'll need to run
yarn compile in
packages/icons to see those changes
reflected before running any of the dev scripts.
This project is made available under the Apache 2.0 License.