npm install away.
The core team members and most contributors do this open source work in their free time. If you use AssemblyScript for a serious task or plan to do so, and you'd like us to invest more time on it, please donate to our OpenCollective. By sponsoring this project, your logo will show up above. Thank you so much for your support!
You are now able to write WebAssembly, without learning a new language, and harness all these benefits WebAssembly might offer you. I think that is kind of powerful. [...] It [AssemblyScript] is absolutely usable, and very enjoyable! - Surma, WebAssembly for Web Developers (Google I/O ’19) (May 8th, 2019)
For general usage instructions, please refer to the documentation instead. The following sets up a development environment of the compiler, for example if you plan to make a pull request:
$> git clone https://github.com/AssemblyScript/assemblyscript.git $> cd assemblyscript $> npm install $> npm link $> npm clean
Note that a fresh clone of the compiler will use the distribution files in
dist/, but after an
npm clean it will run the sources directly through ts-node, which is useful in development. This condition can also be checked by running
asc -v (it is running the sources if it states
-dev). Also please see our contribution guidelines before making your first pull request.
To build an UMD bundle to
dist/assemblyscript.js (depends on binaryen.js), including a browser version of asc to
dist/asc.js (depends on assemblyscript.js):
$> npm run build
Cleaning the distribution files (again):
$> npm run clean
Linting potential changes:
$> npm run check
Running the tests:
$> npm test
Running everything in order (lint, clean, test, build, test):
$> npm run all