d73116509c
Ugh, we need to write out a TypeScript file instead of importing the JSON directly because otherwise the TS compiler will spend an inordinate amount of time doing type inference, which massively slows down type-checking (especially in IDEs and such). The TS file actually uses `JSON.parse` on a stringified version of the JSON instead of just inlining the JSON itself because [apparently it's much faster][1]. [1]: https://www.bram.us/2019/11/25/faster-javascript-apps-with-json-parse/ |
||
|---|---|---|
| .github/workflows | ||
| .vscode | ||
| assets/symbols | ||
| lib | ||
| vendor/bezier-js | ||
| .babelrc | ||
| .gitignore | ||
| README.md | ||
| build-vocabulary.js | ||
| copy-svgs-from-dropbox.sh | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.json | ||
README.md
This is an attempt by Nina Paley (art) and Atul Varma (code) to tinker with procedural art.
Right now there is no particular goal other than to explore various ideas. The project consists of a web site with multiple pages, each of which is and experiment of some kind.
It can be viewed online or iterated on locally using the instructions below.
Quick start
This requires NodeJS. It was started with NodeJS 14.15.4, but hopefully it should work with any recent version.
After cloning the repository and entering it, run:
npm run watch
then visit http://localhost:1234.
Running tests
To run tests interactively, run:
npm run test:watch
Deployment
To deploy the project to GitHub Pages, run:
npm run deploy