revenge-bundle-next/lib/plugins/src/constants.ts

26 lines
580 B
TypeScript
Raw Normal View History

import { callNativeMethodSync } from '@revenge-mod/modules/native'
/**
* The plugin status.
*/
export const PluginStatus = {
PreIniting: 1 << 0,
PreInited: 1 << 1,
Initing: 1 << 2,
Inited: 1 << 3,
Starting: 1 << 4,
Started: 1 << 5,
Stopping: 1 << 6,
}
const { storageRootPath } = callNativeMethodSync(
'revenge.plugins.getConstants',
[],
)
/**
* Absolute path to per-plugin storage directory.
*/
feat!: new repo system + versioning system support + bug fixes BREAKING CHANGES: - New versioning system: Allowing any amount of number segments, with prerelease support. - Any number of segments is supported: 1, 1.0, 1.0.0, 1.0.0.0, ... - Prerelease labels are compared "digit-run", similar to Debian. - Plugins must specify a version. - User-facing plugins should use CalVer. API plugins should use SemVer. Revenge APIs use SemVer while the new `discord` dependency parses the Discord version string directly. - Dependency is now a Map, with support for version ranges and optional. Suggested URL is removed. (See new repo system) - Plugins will now have to declare a dependency on `revenge.api` (Revenge API version) and `discord` (Discord version). - Manifest now requires a format version (currently `1`) New APIs: - lib/plugins/utils: Utilities to format versioning Features: - New repo system: Repository design is inspired by Linux package repositories. - Repos host manifest, versions, channels, download URL/size, and hash for multiple plugins. - New dependency system: Plugins are versioned, and shouldn't break when updates come. Plugins can now declare dependency on supported Discord/Revenge API versions, so they won't break with auto-updates. Dependencies can be optional, but dependency on `revenge.api` and `discord` must be required. Dependents are soft-disabled when dependencies don't satisfy. Once satisfied, the plugin can start again. - All updates for running plugins REQUIRE a reload to prevent stale linking issues. Both native and JS-side. - Update checking is handled entirely by JS. But the native-side still handles installation, indexing, and verification. - Local indexes are updated against remote indexes. Dependency checking always uses local indexes. - Users can add custom repositories and custom their priority order. URL is the identity. - Plugins can now have custom data URI icons instead of being restricted to React Native app assets. - External plugin installs require UI confirmation before installing. - Pending Update and Pending Reload filters in Plugins page. - Ability to browse external plugins in repositories. Official repository will be added soon. Fixes/Refactor: - Refactored Plugin-related settings to a separate "Plugin Settings" plugin. - Masonry layout fixes in landscape. - Updated plugins now show "reload to apply" toast instead. - Removed dead code.
2026-07-25 23:35:23 +07:00
// TODO: is it best to dupe this logic with the native side???
export const pluginStorageDirFor = (id: string) => `${storageRootPath}/${id}`