Open Source TypeScript Runtimes

Deno is a secure by default, open source runtime for JavaScript and TypeScript, providing a productive and secure scripting environment for the modern programmer. It is distributed as a single executable with no dependencies, and takes on the role of both runtime and package manager. It uses a standard browser-compatible protocol for loading modules, which are URLs. Built on top of V8, Rust and TypeScript, Deno has support for TypeScript right out of the box. It has a set of built-in utilities as well as reviewed (audited) standard modules.

Capacitor is an open source native runtime for building Web Native apps. Create cross-platform iOS, Android, and Progressive Web Apps with JavaScript, HTML, and CSS. Capacitor’s native plugin APIs make it extremely easy to access and invoke common device functionality across multiple platforms. Build web-based applications that run equally well across iOS, Android, and as Progressive Web Apps. Access the full Native SDKs on each platform, and easily deploy to the App Stores (and the web). Add custom native functionality with a simple Plugin API, or use existing Cordova plugins with our compatibility layer. Capture images, save photos, and configure hardware parameters like saturation and color balance. Save and read documents, assets, and other content your users need to access via native file systems. Gather critical information about a user’s device location, such as latitude and longitude.

starboard-notebook is an in-browser literate notebook runtime that enables users to write, edit, and interact with computational documents directly in the browser without needing a traditional backend notebook server. The project is built around an innovative runtime that interprets code cells and markdown in a way that feels fluid and interactive, often bridging concepts from classical notebook tools with modern web technologies. Starboard notebooks support multiple languages, and the tooling emphasizes portability, making notebooks viewable and executable even on mobile devices or static sites. Because the runtime runs entirely inside the browser, it removes installation barriers and provides a sandboxed environment for exploration, learning, and sharing. The project plays into a larger ecosystem of in-browser computation and literate programming tools, helping users publish interactive content on the web with minimal setup.

Runtime type system for IO decoding/encoding

We have open-sourced a set of software packages, Runtime Interface Clients (RIC), that implement the Lambda Runtime API, allowing you to seamlessly extend your preferred base images to be Lambda compatible. The Lambda Runtime Interface Client is a lightweight interface that allows your runtime to receive requests from and send requests to the Lambda service. The Lambda NodeJS Runtime Interface Client is vended through npm. You can include this package in your preferred base image to make that base image Lambda compatible. To make it easy to locally test Lambda functions packaged as container images we open-sourced a lightweight web-server, Lambda Runtime Interface Emulator (RIE), which allows your function packaged as a container image to accept HTTP requests. You can install the AWS Lambda Runtime Interface Emulator on your local machine to test your function.

A new full-featured and high-performance TypeScript framework for enterprise applications. High-quality TypeScript libraries and next-gen backend framework. Leverage TypeScript types to the fullest, in completely new ways. A runtime type system for JavaScript, powered by TypeScript types. Deepkit's type compiler makes it possible to use the whole TypeScript type system in any JavaScript runtime for the first time enabling completely new ways of writing data-driven applications. A framework that brings aligned libraries together to make web application development faster, more productive, and easier than ever. Powerful dependency injection container with type expressions to make HTTP routes, CLI commands, and RPC controllers safe, fast, and easy to write. No json configuration files, unnecessary boilerplate, schema files, or code generation: TypeScript is utilized to its fullest capabilities.

GraphQL is a powerful query language for APIs and a runtime for fulfilling those queries with your existing data. It's an elegant approach that solves many problems typically found with REST APIs. For background, we suggest reading this comparison between GraphQL and REST. GraphQL combined with TypeScript helps you develop better type safety with your GraphQL queries, giving you end-to-end typing. In this chapter, we assume a basic understanding of GraphQL, and focus on how to work with the built-in @nestjs/graphql module. The GraphQLModule can be configured to use Apollo server (with the @nestjs/apollo driver) and Mercurius (with the @nestjs/mercurius). We provide official integrations for these proven GraphQL packages to provide a simple way to use GraphQL with Nest. Nest offers two ways of building GraphQL applications, the code first and the schema first methods. You should choose the one that works best for you.

nativescript-google-maps-sdk is a NativeScript plugin that integrates Google Maps into mobile applications. It offers a rich set of features for displaying maps, adding markers, and handling user interactions within NativeScript apps.

It JIT transforms TypeScript into JavaScript, enabling you to directly execute TypeScript on Node.js without precompiling. This is accomplished by hooking node's module loading APIs, enabling it to be used seamlessly alongside other Node.js tools and libraries. Automatic defaults to match your node version, integrate with test runners, debuggers, and CLI tools, compatible with pre-compilation for production. Installing modules locally allows you to control and share the versions through package.json. TS Node will always resolve the compiler from cwd before checking relative to its own installation.ts-node exports a create() function that can be used to initialize a TypeScript compiler that isn't registered to require.extensions, and it uses the same code as register. ts-node supports a variety of options which can be specified via tsconfig.json, as CLI flags, as environment variables, or programmatically.