Engine/framework for three.js
TypeScript definitions for three-engine
<p align="center"> <a href="#"><img src="https://raw.githubusercontent.com/pmndrs/react-three-rapier/HEAD/packages/react-three-rapier/misc/hero.svg" alt="@react-three/rapier" /></a> </p>
Force-directed graph as a ThreeJS 3d object
A simple WebGL/WebGPU-based game framework with Actor-Component logic on top of threejs, with cannon-es for physics.
配置化的开发期用引擎。会生成相关的物体辅助，还有相关的物体控件进行可视化的构建场景。
A BVH implementation to speed up raycasting against three.js meshes.
JavaScript 3D library
Define a data property on an object. Will fall back to assignment in an engine without descriptors.
Lexical is an extensible text editor framework that provides excellent reliability, accessible and performance.
Engine for Shiki using Oniguruma RegExp engine in WebAssembly
A React renderer for Threejs
stand-alone library of threejs examples
useful add-ons for react-three-fiber
Intl.LocaleMatcher ponyfill
[`react-three-fiber`](https://github.com/drcmda/react-three-fiber) support. This package is for version 6 of react-three-fiber
styled() API wrapper package for emotion.
This package is intended for Prisma's internal use
SDF-based text rendering for Three.js
Various utilities related to Three.js
配置化的展示用引擎。可用于查看展示模型，交互事件，动画，dom 组件等等。
Provides fundamental functions for rendering GIS data in Three.js and R3F
Engine for Shiki using JavaScript's native RegExp
A collection of post-processing effects
A simple solution to provide on-demand service access (e.g. port 80 on webserver), where a more robust and secure VPN solution is not available. Essentially, it is a more user-friendly form of "port knocking". The original proof-of-concept implementation was run for almost three years by Demotix, to protect development and staging servers from search engine crawlers and other unwanted traffic.
This talk describes three Ruby usages: * Implementing high-level interface by Ruby. * Using Ruby as a glue language. * Embedding Ruby into a C program for flexibility. All of them have pros and cons. They are trade-off. If a case can ignore cons, we will have pros for the case. Most of Rubyists implement their Ruby applications only by Ruby. This talk shows another options to use Ruby as your convenient tool. If you know another options and trade-offs of them, you will implement your Ruby applications more effectively. This talk uses Droonga, a distributed full-text search engine, as a sample application to describe these Ruby usages. Droonga uses these three Ruby usages.
A Rails Engine wrapping SmarterCSV for CSV importing with three-tier AI header matching (lookup + vector similarity + LLM fallback), batch processing, and import tracking. Only headers are sent to AI — row data never leaves your application.
A Rails engine that wraps PDF.js to provide a full-featured PDF viewer with text and area highlighting, powered by Stimulus controllers and Tailwind CSS. Includes a three-panel layout with outline/thumbnails sidebar, highlight management, and an overridable right sidebar for custom integrations.
KnowBe4, Inc. is a high growth information security company. We are the world’s largest provider of new-school security awareness training and simulated phishing. KnowBe4 was created to help organizations manage the ongoing problem of social engineering. Tens of thousands of organizations worldwide use KnowBe4’s platform to mobilize their end users as a last line of defense and enable them to make better security decisions, every day. We are ranked #1 best place to work in technology nationwide by Fortune Magazine and have placed #1 or #2 in The Tampa Bay Best Workplaces Survey for the last three years. We also just had our 23rd record-setting quarter in a row!
Scrapetor is a Ruby HTML parsing + scraping toolkit. The parser is a native C arena DOM with structural indexes built at parse time and NEON SIMD scanners in the SAX hot loop. A streaming extraction engine compiles the schema DSL into a single forward pass — no DOM materialised, one Ruby boundary crossing per document. On builds where libcurl is available, Scrapetor::Fetcher adds an HTTP/2-capable fetch layer with per-thread connection cache, shared DNS + TLS session pool, in-process gzip / deflate / brotli / zstd decoding, iconv charset transcoding, retry + exponential backoff, ETag / Last-Modified disk cache with bulk revalidation, per-host throttle, cookie jar, basic + bearer auth, proxy, and three bulk concurrency models (parallel_fetch / multi_fetch / streaming multi_each). Scrapetor::Session ties the cookie / auth / throttle / retry policies together. Also ships robots.txt + sitemap.xml parsers, a bounded-memory streaming HTML parser, and structured-data extractors (JSON-LD, OpenGraph, Schema.org, Microdata, RDFa, Twitter Cards). The Net::HTTP-based Scrapetor.fetch is preserved as the no-libcurl fallback.
Contentful API wrapper library exposing an ActiveRecord-like interface
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.