This is a
playground to test code. It runs a full
Node.js environment and already has all of
npm’s 400,000 packages pre-installed, including
@chrisoakman/chessboardjs with all
npm packages installed. Try it out:
@chrisoakman/chessboardjs lists no main file and has no index.js, so it can't be directly required. If this is a mistake, please let us know. It may however contain internal files that you can require manually:
This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.
Please see chessboardjs.com for documentation and examples.
chessboard.js is flexible enough to handle any of these situations with relative ease.
The scope of chessboard.js is limited to "just a board." This is intentional and makes chessboard.js flexible for handling a multitude of chess-related problems.
This is a common source of confusion for new users. [remove?]
Specifically, chessboard.js does not understand anything about how the game of chess is played: how a knight moves, who's turn is it, is White in check?, etc.
Fortunately, the powerful chess.js library deals with exactly this sort of problem domain and plays nicely with chessboard.js's flexible API. Some examples of chessboard.js combined with chess.js: 5000, 5001, 5002
Please see the powerful chess.js library for an API to deal with these sorts of questions.
This logic is distinct from the logic of the board. Please see the powerful chess.js library for this aspect of your application.
Here is a list of things that chessboard.js is not:
chessboard.js is designed to work well with any of those things, but the idea behind chessboard.js is that the logic that controls the board should be independent of those other problems.
# create a build in the build/ directory npm run build # re-build the website npm run website