@plurnk/plurnk-schemes-all 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 PossumTech Laboratories
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,21 @@
+# @plurnk/plurnk-schemes-all
+
+Batteries-included bundle for [plurnk-service](https://github.com/plurnk/plurnk-service)'s external `scheme` discovery. **It ships no code** — it's a single dependency that pulls in every first-party [`@plurnk/plurnk-schemes-*`](https://github.com/plurnk/plurnk-schemes) sibling, **flat**, so one install surfaces them all to the service's scope-agnostic `node_modules` scan (`plurnk.kind:"scheme"`).
+
+```
+npm i @plurnk/plurnk-schemes-all
+```
+
+Bundles:
+
+| | scheme |
+|---|---|
+| `@plurnk/plurnk-schemes-http` | `http://`, `https://` (fetch + headless-Chromium render) |
+
+## Why a bundle, not framework deps
+
+The framework — [`@plurnk/plurnk-schemes`](https://github.com/plurnk/plurnk-schemes) — stays **contract-only** so it has no circular deps and so service's discovery scan can find scheme siblings at the top level of `node_modules`. This aggregator depends on the daughters *directly*, so npm hoists them flat — discovery sees them. The framework arrives transitively as each daughter's exact peer; it is **not** a dependency here (it declares no `plurnk.kind`, so the scan ignores it anyway).
+
+A **third party** publishes their own scheme under their own scope (`@acme/acme-scheme-foo`, `plurnk.kind:"scheme"`) and installs it alongside — service's scan finds it by kind, no bundle membership required (plurnk-service#227). The bundle is just the convenient first-party default, never a gate.
+
+Want a subset? Skip this and depend on the individual scheme packages you want — discovery treats them identically.

package/package.json

@@ -0,0 +1,35 @@
+{
+    "name": "@plurnk/plurnk-schemes-all",
+    "version": "0.1.0",
+    "description": "Batteries-included bundle for plurnk-service's external scheme discovery — installs every first-party @plurnk/plurnk-schemes-* sibling (flat) so one dependency surfaces them all to the scan.",
+    "keywords": [
+        "plurnk",
+        "scheme",
+        "uri",
+        "bundle",
+        "meta"
+    ],
+    "homepage": "https://github.com/plurnk/plurnk-schemes-all#readme",
+    "bugs": {
+        "url": "https://github.com/plurnk/plurnk-schemes-all/issues"
+    },
+    "repository": {
+        "type": "git",
+        "url": "git+https://github.com/plurnk/plurnk-schemes-all.git"
+    },
+    "engines": {
+        "node": ">=25"
+    },
+    "license": "MIT",
+    "author": "@wikitopian",
+    "type": "module",
+    "publishConfig": {
+        "access": "public"
+    },
+    "files": [
+        "README.md"
+    ],
+    "dependencies": {
+        "@plurnk/plurnk-schemes-http": "0.2.0"
+    }
+}