- How do I install darinlarimore/statamic-3d-field in a Laravel Statamic app?
- Install it with Composer using composer require darinlarimore/statamic-3d-field. Statamic addon discovery should register the service provider, but you should still clear Statamic and Laravel caches after installation. If your deployment flow requires publishing package assets, run the package's publish command and rebuild caches before editing content.
- Which Statamic versions does this 3D fieldtype support?
- The declared Composer constraint is statamic/cms ^5.0|^6.0, so the addon is intended for Statamic 5 and Statamic 6. Version 1.1.0 ports the control-panel fieldtype to Vue 3 and registers it inside Statamic.booting() for Statamic 6. Because the same bundle also claims Statamic 5 support, smoke-test the fieldtype in your exact Statamic version rather than relying on the constraint alone.
- What file formats can editors upload for the 3D model field?
- The fieldtype is designed for GLB and GLTF 3D model files. Editors can drag and drop a model or select an existing asset from the Statamic asset library. Other 3D formats are not listed as supported, so convert them to GLB or GLTF before upload.
- How does the live 3D preview work in the Statamic control panel?
- The control-panel preview uses Google's model-viewer custom element to render an interactive 3D viewer. Editors can rotate and inspect the model before saving or publishing the entry. The package documentation does not clearly state whether model-viewer is bundled, loaded from a CDN, or expected from the host app, so verify its loading behavior in your environment.
- How do I output the 3D model asset in Antlers or Blade templates?
- The fieldtype stores a Statamic asset value that you can read in Antlers or Blade like any other asset field. In Antlers, output the asset URL from the field; in Blade, retrieve the asset and call its url() method. Confirm the exact field handle from your fieldset configuration.
- Does this package work with Statamic 6 and Vue 3?
- Yes, version 1.1.0 is primarily a Statamic 6 readiness release. It moves the fieldtype from Vue 2 to Vue 3, registers inside Statamic.booting(), and externalizes Vue for the Statamic 6 control panel. It also keeps a widened statamic/cms ^5.0|^6.0 constraint, but real control-panel testing is still required.
- What are the risks of upgrading this 3D fieldtype to 1.1.0 on Statamic 5?
- Treat 1.1.0 on Statamic 5 as a medium-risk upgrade because a Vue 3 IIFE bundle is being used in a potentially different control-panel runtime. Watch for Vue template compilation issues, model-viewer custom element lifecycle problems, stale cached control-panel assets, and visual or behavioral changes from replacing toggle-input with ui-switch. Run create, edit, preview, and save flows in staging before production.
- Do I need to publish or rebuild assets after installing or upgrading the addon?
- The package ships a built Vue 3 IIFE control-panel bundle, so a full frontend build is not normally required. However, asset caching can serve stale control-panel JavaScript after an upgrade. Clear Statamic and Laravel caches, run any documented vendor publish step, and hard-refresh the control panel when validating the new version.
- What should I test before using this fieldtype in production?
- Test the fieldtype in the actual Statamic control panel by creating and editing an entry, uploading or selecting a GLB or GLTF file, confirming the model-viewer preview renders, and saving the entry. Check the browser console for Vue and custom-element errors, and verify the saved asset outputs correctly in Antlers or Blade. Also test behavior if model-viewer fails to load and confirm assets are not stale after deployment.
- Is darinlarimore/statamic-3d-field a good alternative to a general Laravel 3D viewer package?
- This is not a general Laravel 3D viewer library; it is a Statamic control-panel fieldtype for managing 3D model assets. If you need a CMS field with an editor preview in Statamic, it fits that use case directly. If you only need to render a model-viewer component on a Laravel page, using model-viewer or a dedicated frontend 3D library may be simpler.