ChakraCore
react-navigation
Our great sponsors
| ChakraCore | react-navigation | |
|---|---|---|
| 15 | 66 | |
| 9,031 | 23,258 | |
| 0.2% | 0.5% | |
| 5.3 | 9.3 | |
| 6 days ago | 7 days ago | |
| JavaScript | TypeScript | |
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ChakraCore
-
This year in Servo: over 1000 pull requests and beyond
I thought it would be a fun weird project to make Servo work with MS' abandoned JavaScript engine:
https://github.com/chakra-core/ChakraCore
Of course it is written in C++ and you'd probably want a pure Rust browser. But it is sad seeing that fairly complete open source JIT JavaScript engine sit and rot.
-
Microsoft defends Edge's predatory practices with cringe reply on X
The JS engine is open source: https://github.com/chakra-core/ChakraCore
-
A list of JavaScript engines, runtimes, interpreters
ChakraCore
-
Roll your own JavaScript runtime, pt. 3
Not to forget the engine Charka: https://github.com/chakra-core/ChakraCore
The only bit of the old Edge that had its source emancipated. It was/is? quite performant.
-
Have you deployed Microsoft Todo to end users? How did you deploy it?
As a Linux user, I very much think Microsoft should have continued Trident and Chakra. Apple also should have continued releasing Safari for Windows. Our web QA setup was entirely built around Macs back then, but it was great to be able to test sites with Safari on Windows, and to have another responsive browser on Win32.
-
The Javascript Engine
Edge was initially using Chakra but has been rebuilt using Chromium and the V8 engine.
-
Crystal's Interpreter (2021)
https://github.com/chakra-core/ChakraCore/wiki/Architecture-...
I've found the source code to be quite readable too - albeit from a bug-finding perspective, not a strictly pedagogical one.
-
Exploring React Native’s new architecture
Furthermore, the new architecture decouples the JavaScript interface from the engine, enabling the use of other JavaScript engines such as Hermes, V8, or Chakra.
-
How web browsers work - executing the Javascript (part 5, with illustrations)💻🌠
ChakraCore
-
Enumerating and analyzing 40 non-V8 JavaScript implementations
I am astonished at the omission of ChakraCore, open sourced by Microsoft but sadly abandoned by them after they switched Edge to Chromium: https://github.com/chakra-core/ChakraCore. But it looks like it’s still chugging along as a community effort rather than being completely abandoned.
react-navigation
-
Weird redirect issue with Stack Navigator/Expo I do not understand, please help
UPDATE: Looks like I'm not the only one https://github.com/react-navigation/react-navigation/issues/10988
-
Why would React-Navigation documentation not include some of the most important props and functionalities?
Does this work on @react-navigation/native-stack or only @react-navigation/stack ? I know you said
- How to "Refresh" App Screen Without user Input?
- Handle go back in nested navigation.
- React native for Linux app development in 2023
- How would you create this horizontal/scrollable list? with a different style for the active tab?
-
React Native go-to packages for every mobile app
React Navigation
- Best way to create react app from scratch
-
How would i go about building this?
you're more than likely going to need https://reactnavigation.org/ for pages and tabs/bottom nav.
-
React Native Navigation??
Wow, that's A LOT, but when You do a simple setup does it just work when You just follow the reactnavigation.org docs procedure? because when I do I, First I get the error, node modules not found then after restarting my PC I get these error: FAILURE: Build completed with 2 failures. 1: Task failed with an exception. ----------- * Where: Build file 'C:\Users\user\Documents\WORK\ENGINEERING\PROJECTS\REACT NATIVE PROJE CTS\1LEARNING\Nav1\node_modules\react-native-screens\android\build.gradle' line: 33 This is what I have on line 33: apply plugin: 'kotlin-android' * What went wrong: A problem occurred evaluating project ':react-native-screens'. > Could not initialize class org.jetbrains.kotlin.gradle.plugin.KotlinGradleBuil dServices * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output.
What are some alternatives?
Jint - Javascript Interpreter for .NET
react-native-chart-kit - 📊React Native Chart Kit: Line Chart, Bezier Line Chart, Progress Ring, Bar chart, Pie chart, Contribution graph (heatmap)
hermes - A JavaScript engine optimized for running React Native.
react-keycloak - React/React Native/NextJS/Razzle components for Keycloak
V8 - The official mirror of the V8 Git repository
react-native-tab-view - A cross-platform Tab View component for React Native
v8.dev - The source code of v8.dev, the official website of the V8 project.
react-native-simple-toast - Cross-platform Toast experience for React Native
AutoHotkey-jk - AutoHotkey, running JavaScript.
react-native-bottom-sheet - A performant interactive bottom sheet with fully configurable options 🚀
astexplorer - A web tool to explore the ASTs generated by various parsers.
ignite-bowser - Bowser is now re-integrated into Ignite CLI! Head to https://github.com/infinitered/ignite to check it out.