Build an Angular library compatible with AoT compilation and Tree shaking
realistic password strength estimation
MongoDB connection strings, based on the WhatWG URL API
ECC JS code based on JSBN
The Czech language package for zxcvbn-ts
TypeScript definitions for jsbn
Checksum utility for node
Edge-cs: C# compiler for Edge.js
Redis utilities for redis instrumentations
a few common utility template tags for ES2015
A common tooling library used by the googleapis npm module. You probably don't want to use this directly.
Utilities for SQL instrumentations
Common functionality for ts-morph packages.
Microsoft Authentication Library for js
Common components for Cloud APIs Node.js Client Libraries
A library for working with Unicode character sets
Storybook framework-agnostic API
Syntax tree data structure and parser interfaces for the lezer parser
Find the common ancestor of 2 or more paths on Windows or Unix
get structured callsite information
[更新日志](./CHANGELOG.md)
Common library for code that's used across the Client, Worker, and/or Workflow
Edge-cs: run C# and node.js code in-process with edge.js
Common utility functions for oas-kit
A metrics library for eBPF programs.
Shared utilities for codemetrics -- file scanning, output formatting, CLI patterns
Shared GCS credential and client types for the faucet-stream ecosystem
Geobacter driver internal shared code. Do not use.
This crate contains basic statistics utilities and abstractions to be re-used and applied throughout both the client and gateway implementations
Apache OpenDAL observe metrics common components
Shared primitives for every rsomics-* crate (errors, CLI scaffold, runner, progress, exit codes).
The Programming Exercise Markup Language (PEML) is intended to be a simple, easy format for CS and IT instructors of all kinds (college, community college, high school, whatever) to describe programming assignments and activities. We want it to be so easy (and obvious) to use that instructors won't see it as a technological or notational barrier to expressing their assignments. We intend for this format to be something that authors of automated grading tools can adopt, so they can provide a very easy, low-energy onboarding path for existing instructors to get programming activities into such tools. As a result, this notation leans heavily on supporting authors and streamlining common cases, even if this may require more work on the part of tool developers--the goal is to make it super easy for authors of programming activities, not to fit into a specific auto-grader or simplify tasks for tool writers. For more details, see the PEML website.
Diff and patch tables
Diff and patch tables
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.