TKO houses the monorepo of Knockout.
To install use one of the usual package managers e.g.
yarn add @tko/build.reference
npm install @tko/build.reference
The Knockout build has some backwards compatibility that is not in the reference build. See the build differences, here: https://tko.io/3to4
It's available as
@tko/build.knockout, and over CDN:
||Clone the repository.|
||Ensure yarn is globally available|
||Install local node packages and link tko modules|
||Run all tests. See below.|
||Run all tests and watch for changes. See below.|
||Build tko[.module][.es6][.min].js files, where
||Bump versions and publish to npm registry|
package.json => scripts for more commands that can be executed with
In each individual
packages/*/ directory, you can also run (presuming
karma are installed globally):
||Test the local package, where COMMAND is e.g.
||Build the package into the local
yarn test and
yarn watch commands can be used in the root directory, where it will run across all tests, or alternatively in any
packages/*/ directory to run tests
specific to that package.
Optional arguments to
yarn test include:
--sauce— use Sauce Labs to test a variety of platforms; requires an account at Sauce Labs and
SAUCE_ACCESS_KEYto be set in the environment.
--noStartConnect— Do not start a new Sauce Connect proxy instance for every test; requires that Sauce Connect be already running.
Note that running
rollup will create a
visual.html file that shows the proportional size of imports into each package.
TKO aims to become a base for future versions of Knockout. The objectives include:
There's an issue for that.
MIT license - http://www.opensource.org/licenses/mit-license.php.