You want to contribute to LiSc? Awesome! Any form of help is greatly appreciated (contributions/pull requests, suggestions, tips, bug reports,...).
Join the Litags Discord to get in touch (LiTags is a browser extension for lichess.org I implemented).
Make an issue. Make sure you list the steps to reproduce the problem and it is not a trivial problem or demands unrealistic dev time to fix. Issues reports of very minimal effort may be closed.
Issue tickets on features that lack potential or effectiveness are not useful and may be closed. Before creating a ticket, please first try to discuss it on the Litags Discord in appropriate channels to gauge feedback. When ready: make an issue ticket.
npm run start will start a dev server at localhost:9000 which will hot reload any changes to the source you make in the meantime.
npm run build will clean build/, then build LiSc (prod mode). Be wary of the publicPath: '/lisc/' in webpack.production.js and adapt accordingly for your needs.
npm run deploy will build LiSc in production mode and push to the gh-pages branch of the repo.
npm run lint will verify the code style (and point out any errors) of all .ts .js and files in src/
using ESLint with typescript support by TypeScript ESLint.