Repository navigation
Getting Started
Start with a data container. It exercises real metadata, resources and hashes without loading executable plugin code or depending on Qt.
This walkthrough targets 0.1.3. Use its matching tag:
mkdir ylplugin-work
cd ylplugin-work
git clone --branch v0.1.3 --depth 1 https://github.com/YoungLionOrganization/YLPlugin.git sourcesource/examples/artifacts/data.ylplugin contains catalog.json, whose total
is 42. The same directory also contains real WASM and RCC fixtures. Keep those
for later; opening a data fixture requires no runtime adapter.
Create/activate a virtual environment and install:
python -m venv .venv
# POSIX: . .venv/bin/activate
# PowerShell: .venv\Scripts\Activate.ps1
python -m pip install ylplugin==0.1.3
ylplugin --version
ylplugin metadata source/examples/artifacts/data.ylplugin --jsonFrom ylplugin-work, save and run:
import json
from ylplugin import Library
with Library().open("source/examples/artifacts/data.ylplugin") as package:
package.validate()
data = json.loads(package.read("catalog.json"))
assert data["total"] == 42
print(package.targets)The platform wheel provides a matching runtime. If no compatible wheel exists, read Installation and Builds rather than mixing another platform's native library with the facade.
Create a separate consumer directory:
mkdir node-client
cd node-client
npm init -y
npm install @younglionorganization/ylplugin@0.1.3Save read.mjs and run node read.mjs:
import {Package} from '@younglionorganization/ylplugin';
const packageFile = '../source/examples/artifacts/data.ylplugin';
const plugin = new Package(packageFile);
try {
plugin.validate();
console.log(JSON.parse(plugin.read('catalog.json')).total);
} finally {
plugin.close();
}TypeScript declarations and CommonJS exports ship in the same package. The SDK uses Node-API; installing it does not create a browser runtime.
Open parsed bounded structure/metadata. Validation checked profile and resource integrity. Read returned hash-verified resource bytes. No publisher identity was authenticated because this fixture is unsigned; no code was activated and no permissions were granted.
Next, author your own container, integrate a host or select the Java/Kotlin SDK. The canonical walkthrough also explains CLI inspection.
YLPlugin · Repository · Releases · Issues · Support · LGPLv3 · Maintained by Cavanshirpro.
Release guide 0.1.3; source development 0.1.4; later features are tracked in the roadmap. Normative contracts: container and profile.