Package Exports
- @infinite-table/infinite-react
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@infinite-table/infinite-react) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Table Of Contents
Installation
npm install @infinite-table/infinite-react --saveDocumentation
Our approach with the InfiniteTable is to go documentation first. From our developer experience we know that most software products lack a good documentation. So we want to be different and start with the documentation first since our purpose is to have an outstanding documentation that developers can actually use.
Development process
You can start the examples by running:
npm run devRunning the docs
npm run docsTesting
Infinite Table is built with extensive end-to-end testing via headless chrome (more exactly, puppeteer). To execute the tests you have to run:
$ npm run testTest pages are found in tests folder - which is part of a nextjs app where every file ending with .page.tsx is a page/route, while it's sibling file with the same name, but ending in .test.tsx is the actual test code. The test code is visiting the sibling page/route, to load the page and executes assertions against the test page.
The test command command above does 3 things:
- compiles the nextjs app found in the examples folder - runs
next build && next export, which creates anoutfolder with the resulting examples/tests app - starts a webserver that serves the generated
outfolder on localhost:3000 - runs jest+puppeteer against the app served at localhost:3000
Testing in development
If you want to run the tests in dev mode, to get feedback sooner, you need to run the following (in the source/examples folder):
npm run dev- to run the nextjs app in development, on port3000npm run test:watchto run jest on changed files - optionally add a test path pattern likenpm run test:watch -- --testPathPattern=x/y/z