core url lib extension
PostCSS plugin to import CSS files
JavaScript utilities with respect to emerging standard
A set of efficient utilities that extend the use of JSON (streaming, estimate size, NDJSON/JSONL, etc.)
ECMAScript extensions and shims
Timers extensions
Replaces a file extension with another one.
MCP Apps SDK — Enable MCP servers to display interactive user interfaces in conversational clients.
A tool to open and run web extensions
Get the file extension and MIME type from a file
Extensions to Node.js child_process module
m3u8 parser
List of known file extensions and their MIME types
Lightweight library for downloading and concatenating HLS audio segments in the browser.
A command line tool to help build, run, and test web extensions
SAP Fiori Tools – UI5 Tooling
A set of cool extensions for OpenLayers (ol) in node modules structure
TypeScript definitions for webgl-ext
Type definitions for ol-ext
Help command for node, partner of minimist and commist
Type definitions for web-ext CLI options
JSON-LD serializer that implements the RDF/JS Sink interface and supports different output styles
An implementation of the WHATWG URL Standard's URL API and parsing machinery
JSON Schema validation for Human
simple-navigation-ext is an extension of andi schacke's library and add the feature to explicitly exclude urls from highlighting.
Provides an SCM agnostic way to manage subprojects with a workflow similar to the scm:externals feature of subversion. It's particularly useful for rails projects that have some plugins managed by svn and some managed by git. For example, "ext install git://github.com/rails/rails.git" from within a rails application directory will realize that this belongs in the vendor/rails folder. It will also realize that this URL is a git repository and clone it into that folder. It will also add the vendor/rails folder to the ignore feature for the SCM of the main project. Let's say that the main project is being managed by subversion. In that case it adds "rails" to the svn:ignore property of the vendor folder. It also adds the URL to the .externals file so that when this project is checked out via "ext checkout" it knows where to fetch the subprojects. There are several other useful commands, such as init, touch_emptydirs, add_all, export, status. There's a tutorial at http://nopugs.com/ext-tutorial The reason I made this project is that I was frustrated by two things: 1. In my opinion, the workflow for svn:externals is far superior to git-submodule. 2. Even if git-submodule was as useful as svn:externals, I would still like a uniform way to fetch all of the subprojects regardless of the SCM used to manage the main project.
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.