@dcl/asset-packs 2.11.7 → 2.12.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +36 -0
- package/bin/index.js +3170 -7068
- package/dist/bin/index.js +3170 -7068
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -118,6 +118,42 @@ Go to the `packages/creator-hub` in this monorepo and do this:
|
|
|
118
118
|
|
|
119
119
|
Now you are all set, you can start developing the SDK7 scene in this repo, use it from the local Builder and test it by previewing the scene, which should use your local Builder Server serving the development javascript files.
|
|
120
120
|
|
|
121
|
+
### Testing New Assets in the Inspector
|
|
122
|
+
|
|
123
|
+
The inspector fetches the asset catalog at runtime from S3. If `latest/catalog.json` is unreachable (e.g. on a pre-merge PR branch, in CI, or offline), it automatically falls back to the `catalog.json` bundled in the `@dcl/asset-packs` npm package — so the inspector always loads.
|
|
124
|
+
|
|
125
|
+
When you add a **new** asset locally it won't appear in the Asset Packs tab automatically because neither the CDN nor the bundled catalog knows about it yet. There are two options:
|
|
126
|
+
|
|
127
|
+
#### Option 1 — Docker (full local stack, recommended)
|
|
128
|
+
|
|
129
|
+
The existing docker-compose setup handles everything. `npm run upload` now also uploads `catalog.json` as `asset-packs/latest/catalog.json` to MinIO, mirroring what CI does on S3.
|
|
130
|
+
|
|
131
|
+
Follow the steps in [Local Development](#local-development) above, then open the inspector with:
|
|
132
|
+
|
|
133
|
+
```
|
|
134
|
+
http://localhost:8000/?contentUrl=http://localhost:9000/asset-packs
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
Both the catalog listing and all asset files are served locally — full end-to-end testing with no remote CDN needed.
|
|
138
|
+
|
|
139
|
+
#### Option 2 — Upload to dev CDN via PR
|
|
140
|
+
|
|
141
|
+
Push your branch and comment `/upload-assets` on the pull request (org members only). The CI will upload all asset files from your branch to the development CDN (`https://builder-items.decentraland.zone`) and post a comment confirming the upload.
|
|
142
|
+
|
|
143
|
+
Then configure the inspector to use the dev CDN:
|
|
144
|
+
|
|
145
|
+
```
|
|
146
|
+
VITE_ASSET_PACKS_CONTENT_URL=https://builder-items.decentraland.zone
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
Or when opening the inspector directly:
|
|
150
|
+
|
|
151
|
+
```
|
|
152
|
+
http://localhost:8000/?contentUrl=https://builder-items.decentraland.zone
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
The catalog pointer (`latest/catalog.json`) is only updated on merge to `main`, so the Asset Packs tab will still show the currently published catalog — but the asset files themselves will be available for loading.
|
|
156
|
+
|
|
121
157
|
### Troubleshooting
|
|
122
158
|
|
|
123
159
|
#### Missing `@dcl/ecs` dependency
|