You can stay up-to-date on progress by following the MSEdge developer blog.
|Ubuntu 16.04 (x64)|
|Ubuntu 16.04 (x64 static)|
|OS X 10.9 (x64 static)|
If you see badges reading "Build: Unknown" it is likely because a build was skipped due to changes being only in files known not to affect the health of the build.
Above is a table of our rolling build status. We run additional builds on a daily basis. See Build Status for the status of all builds.
If you believe you have found a security issue in ChakraCore, please share it with us privately following the guidance at the Microsoft Security TechCenter. Reporting it via this channel helps minimize risk to projects built with ChakraCore.
- ChakraCore Architecture
- Quickstart Embedding ChakraCore
- JSRT Reference
- Contribution guidelines
- Blogs, talks and other resources
You can build ChakraCore on Windows 7 SP1 or above, and Windows Server 2008 R2 or above, with either Visual Studio 2013 or 2015 with C++ support installed. Once you have Visual Studio installed:
- Clone ChakraCore through
git clone https://github.com/Microsoft/ChakraCore.git
Build\Chakra.Core.slnin Visual Studio
- Build Solution
More details in Building ChakraCore.
Alternatively, you can get pre-built ChakraCore binaries from our NuGet Packages.
Once built, you have a few options for how you can use ChakraCore:
- The most basic is to test the engine is running correctly with the ch.exe binary. This app is a lightweight hosting of JSRT that you can use to run small applications. After building, you can find this binary in:
- You can embed ChakraCore in your applications - see documentation and samples.
document.write() are additional APIs that are not available by default and would need to be provided. For debugging, you may instead want to use
Contributions to ChakraCore are welcome. Here is how you can contribute to ChakraCore:
- Submit bugs and help us verify fixes
- Submit pull requests for bug fixes and features and discuss existing proposals
- Chat about @ChakraCore on Twitter
Please refer to Contribution guidelines for more details.
Code licensed under the MIT License.
For details on our planned features and future direction please refer to our roadmap.