@bedrock-oss/add-on-registry 1.0.0 → 1.0.2

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2025 Bedrock OSS
-
-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.
+MIT License
+
+Copyright (c) 2025 Bedrock OSS
+
+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

@@ -1,48 +1,48 @@
-# Add-On Registry
-A registry for Minecraft Bedrock Add-Ons and their basic meta-data. This is intended to be used by features such as WAILA-Add-Ons to display accurate information about packs.
-
-If you are an Add-On creator, you are welcome to add your pack to the registry so that it can be displayed accurately in other Add-Ons that display information about content from various Add-Ons.
-
-
-## Contribution
-To add your project(s), create a new JSON file or edit one inside the `/registry` folder with the required details, and submit it via pull-request.
-Your pull-request will automatically merge all JSON files together into 1 `registry.js`.
-
-### Steps
-1. Create a new JSON file or edit one inside the `/registry` folder.  
-   - If you're a "new" creator, the filename should be your creator/studio name (e.g. `ascent.json`, `spark.json`).
-2. Follow the structure used in the other files. Example:
-   ```json
-    {
-        "ascent_paint": {
-            "name": "Paint",
-            "creator": "ASCENT"
-        }
-    }
-   ```
-3. Commit your JSON file, then open a pull request.
-
-### Notes
-- The **key** should be the ID/namespace of your Add-On (the same namespace you use for blocks, entities, etc.).
-- `name`: Display name of your Add-On.
-- `creator`: Name of the creator or studio.
-- Duplicate keys are not allowed. The build will fail if a namespace is already taken.
-- Please use 4 spaces for indentation in your JSON file for consistency across all creator files.
-
-## Including it in your pack
-To use the registry in your project, install it via NPM from this repository:
-```
-npm i https://github.com/Bedrock-OSS/add-on-registry
-```
-
-You can now use it in your project like this:
-```javascript
-import { Registry } from "bedrock-add-on-registry"
-
-function getAddOnName(identifier) {
-    const namespace = identifier.split(":")[0];
-    const entry = Registry[namespace];
-    // Use the namespace itself as fallback
-    return entry ? entry.name : namespace;
-}
+# Add-On Registry [![npm version](https://img.shields.io/npm/v/@bedrock-oss/add-on-registry)](https://www.npmjs.com/package/@bedrock-oss/add-on-registry)
+A registry for Minecraft Bedrock Add-Ons and their basic meta-data. This is intended to be used by features such as WAILA-Add-Ons to display accurate information about packs.
+
+If you are an Add-On creator, you are welcome to add your pack to the registry so that it can be displayed accurately in other Add-Ons that display information about content from various Add-Ons.
+
+
+## Contribution
+To add your project(s), create a new JSON file or edit one inside the `/registry` folder with the required details, and submit it via pull-request.
+Your pull-request will automatically merge all JSON files together into one file `registry.js` that is not tracked by Git but published to NPM.
+
+### Steps
+1. Create a new JSON file or edit one inside the `/registry` folder.  
+   - If you're a "new" creator, the filename should be your creator/studio name (e.g. `ascent.json`, `spark.json`).
+2. Follow the structure used in the other files. Example:
+   ```json
+    {
+        "ascent_paint": {
+            "name": "Paint",
+            "creator": "ASCENT"
+        }
+    }
+   ```
+3. Commit your JSON file, then open a pull request.
+
+### Notes
+- The **key** should be the ID/namespace of your Add-On (the same namespace you use for blocks, entities, etc.).
+- `name`: Display name of your Add-On.
+- `creator`: Name of the creator or studio.
+- Duplicate keys are not allowed. The build will fail if a namespace is already taken.
+- Please use 4 spaces for indentation in your JSON file for consistency across all creator files.
+
+## Including it in your pack
+To use the registry in your project, install it via NPM from this repository:
+```
+npm i @bedrock-oss/add-on-registry
+```
+
+You can now use it in your project like this:
+```javascript
+import { Registry } from "@bedrock-oss/add-on-registry"
+
+function getAddOnName(identifier) {
+    const namespace = identifier.split(":")[0];
+    const entry = Registry[namespace];
+    // Use the namespace itself as fallback
+    return entry ? entry.name : namespace;
+}
 ```

package/package.json

@@ -1,32 +1,32 @@
-{
-    "name": "@bedrock-oss/add-on-registry",
-    "version": "1.0.0",
-    "description": "A registry for Minecraft Bedrock Add-Ons and their basic meta-data. This is intended to be used by features such as WAILA-add-ons to display accurate information about packs.",
-    "main": "registry.js",
-    "type": "module",
-    "types": "types.d.ts",
-    "repository": {
-        "type": "git",
-        "url": "git+https://github.com/Bedrock-OSS/add-on-registry.git"
-    },
-    "keywords": [
-        "Minecraft"
-    ],
-    "author": "Bedrock-OSS",
-    "license": "MIT",
-    "bugs": {
-        "url": "https://github.com/Bedrock-OSS/add-on-registry/issues"
-    },
-    "homepage": "https://github.com/Bedrock-OSS/add-on-registry#readme",
-    "scripts": {
-        "build": "node scripts/build-registry.js",
-        "prepublishOnly": "npm run build"
-    },
-    "files": [
-        "registry.js",
-        "types.d.ts"
-    ],
-    "publishConfig": {
-        "access": "public"
-    }
-}
+{
+    "name": "@bedrock-oss/add-on-registry",
+    "version": "1.0.2",
+    "description": "A registry for Minecraft Bedrock Add-Ons and their basic meta-data. This is intended to be used by features such as WAILA-add-ons to display accurate information about packs.",
+    "main": "registry.js",
+    "type": "module",
+    "types": "types.d.ts",
+    "repository": {
+        "type": "git",
+        "url": "git+https://github.com/Bedrock-OSS/add-on-registry.git"
+    },
+    "keywords": [
+        "Minecraft"
+    ],
+    "author": "Bedrock-OSS",
+    "license": "MIT",
+    "bugs": {
+        "url": "https://github.com/Bedrock-OSS/add-on-registry/issues"
+    },
+    "homepage": "https://github.com/Bedrock-OSS/add-on-registry#readme",
+    "scripts": {
+        "build": "node scripts/build-registry.js",
+        "prepublishOnly": "npm run build"
+    },
+    "files": [
+        "registry.js",
+        "types.d.ts"
+    ],
+    "publishConfig": {
+        "access": "public"
+    }
+}

package/registry.js

@@ -221,6 +221,22 @@ export const Registry = {
         name: "Auto Factory",
         creator: "Team Metallurgy",
     },
+    twf_jb: {
+        name: "Chomp",
+        creator: "The World Foundry",
+    },
+    twfae_cos: {
+        name: "Lamp Lights",
+        creator: "The World Foundry",
+    },
+    twf_bmt: {
+        name: "Bubble",
+        creator: "The World Foundry",
+    },
+    twf_calm: {
+        name: "C.A.L.M.",
+        creator: "The World Foundry",
+    },
     tomhmagic_realight: {
         name: "Realight Reimagined",
         creator: "Tomhmagic Creations",

package/types.d.ts

@@ -1,6 +1,6 @@
-interface RegistryEntry {
-    name: string
-    creator: string
-}
-type RegistryMap = Record<string, RegistryEntry>
-export const Registry: RegistryMap
+interface RegistryEntry {
+    name: string
+    creator: string
+}
+type RegistryMap = Record<string, RegistryEntry>
+export const Registry: RegistryMap