Aucune description

Suwei Chen 8d89409f07 [CVE-2017-8751]Type confusion casting undefined with TypeOfPrototypeObjectDictionary type il y a 8 ans
Build df8988ca7d Preparing for release 1.7.1 il y a 8 ans
bin 9d6d183387 Changing utf8 conversion codex to improve perf and safety il y a 8 ans
jenkins 17d2228d89 Sanitize non-ASCII files in sources and tools. il y a 8 ans
lib 8d89409f07 [CVE-2017-8751]Type confusion casting undefined with TypeOfPrototypeObjectDictionary type il y a 8 ans
manifests 11d5ae3f35 Add event tracing function in test build il y a 8 ans
pal e4d3a1b07e Partial implementation of Intl with ICU for Windows and xplat. il y a 8 ans
test ec180eb879 [CVE-2017-8740] Fix bad byte code gen for 'with'. The original (conservative) fix for this issue relied on marking scopes as containing 'with'. But because block scopes are created lazily, we can miss the opportunity to mark a scope. Instead, implementing a more accurate fix that marks symbols that are referenced from within 'with' statements as needing scope objects if they are closure-captured. il y a 8 ans
tools 17d2228d89 Sanitize non-ASCII files in sources and tools. il y a 8 ans
.gitattributes e0c61b3923 Restore .gitattributes (accidentally removed in 02a02c3a5) il y a 8 ans
.gitignore 226f1c992d runtests: lldb debugger support il y a 8 ans
CMakeLists.txt d1e0ba78af xplat: add debug symbols to test build il y a 8 ans
CONTRIBUTING.md f2a72ce083 Add a copy of the security notice to CONTRIBUTING.md. il y a 10 ans
LICENSE.txt c51ae0b7ef License: Update License file and Third Party Notices il y a 9 ans
README.md 6b2275b183 Readme: Add link to wiki for pre-built binaries. il y a 8 ans
RegenAllByteCode.cmd 9049b2ca99 Add RegenAllByteCode.cmd script il y a 9 ans
RegenAllByteCodeNoBuild.cmd 188182c065 Add RegenAllByteCodeNoBuild.cmd il y a 8 ans
THIRD-PARTY-NOTICES.txt e0eef49629 Use Third-party yargs-parser for command-line argument parsing il y a 8 ans
build.sh 5f03892f6b Fixing ninja builds as part of parent make il y a 8 ans
netci.groovy bc20becc48 Adding the ability to dump perf.map files on non-windows systems il y a 8 ans

README.md

ChakraCore

Licensed under the MIT License

ChakraCore is the core part of Chakra, the high-performance JavaScript engine that powers Microsoft Edge and Windows applications written in HTML/CSS/JS. ChakraCore supports Just-in-time (JIT) compilation of JavaScript for x86/x64/ARM, garbage collection, and a wide range of the latest JavaScript features. ChakraCore also supports the JavaScript Runtime (JSRT) APIs, which allows you to easily embed ChakraCore in your applications.

You can stay up-to-date on progress by following the MSEdge developer blog.

Build Status

Debug Test Release
Windows (x64) x64debug x64test x64release
Windows (x86) x86debug x86test x86release
Windows (ARM) armdebug armtest armrelease
Ubuntu 16.04 (x64)[a] linux_a_debug linux_a_test linux_a_release
Ubuntu 16.04 (x64)[s] linux_s_debug linux_s_test linux_s_release
Ubuntu 16.04 (x64)[s][n] * linux_sn_test *
OS X 10.9 (x64)[a] osx_a_debug osx_a_test osx_a_release
OS X 10.9 (x64)[s][n] * osx_sn_test *

[a] Static | [s] Shared | [n] NoJIT | * Omitted

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 and additional details.

Security

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.

Documentation

Building ChakraCore

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
  • Open Build\Chakra.Core.sln in Visual Studio
  • Build Solution

More details in Building ChakraCore.

Alternatively, see Getting ChakraCore binaries for pre-built ChakraCore binaries.

Using ChakraCore

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:
    • Build\VcBuild\bin\${platform}_${configuration}
    • (e.g. Build\VcBuild\bin\x64_debug)
  • You can embed ChakraCore in your applications - see documentation and samples.
  • Finally, you can also use ChakraCore as the JavaScript engine in Node. You can learn more by reading how to use Chakra as Node's JS engine

A note about using ChakraCore: ChakraCore is the foundational JavaScript engine, but it does not include the external APIs that make up the modern JavaScript development experience. For example, DOM APIs like 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 print().

Contribute

Contributions to ChakraCore are welcome. Here is how you can contribute to ChakraCore:

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Please refer to Contribution Guidelines for more details.

License

Code licensed under the MIT License.

Roadmap

For details on our planned features and future direction please refer to our Roadmap.

Contact Us

If you have questions about ChakraCore, or you would like to reach out to us about an issue you're having or for development advice as you work on a ChakraCore issue, you can reach us as follows:

  • Open an issue and prefix the issue title with [Question]. See Question tag for already-opened questions.
  • Discuss ChakraCore with the team and the community on our Gitter Channel.
  • You can also start private messages with individual ChakraCore developers via Gitter.