@needle-tools/materialx 1.7.0-next.8333b4d → 1.7.0-next.9ec2906

package/CHANGELOG.md

@@ -16,6 +16,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ### Fixed
 - Removed browser-hostile runtime imports of `three/src`, `UniformsLib`, and WebGL-only Three.js exports so the package can share the host application's Three.js import map in WebGL and WebGPU contexts.
+- Added the JSON module import attribute for `package.json` so raw browser ESM imports can read the package version without MIME errors.
 - Corrected material parameter editing for color values, environment controls, and graph-loaded materials in the viewer examples.
 - Kept viewer debug panels and camera controls consistent across the material library, graph, shadows, and complex scenes.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@needle-tools/materialx",
   "description": "MaterialX material support for three.js and Needle Engine – render physically based MaterialX shaders in the browser via WebAssembly",
-  "version": "1.7.0-next.8333b4d",
+  "version": "1.7.0-next.9ec2906",
   "type": "module",
   "license": "PolyForm-Noncommercial-1.0.0",
   "main": "index.js",

package/src/constants.js

@@ -1,5 +1,5 @@
-// Bare JSON import works in bundlers (Vite, Webpack, Rollup) and keeps the
-// runtime version tied to package.json. Node.js 22+ requires JSON import
-// attributes, so unit tests use tests/unit/register-json-loader.js.
-import pkg from '../package.json';
+// Keep the runtime version tied to package.json. The import attribute is
+// required by browsers and Node.js for JSON modules; bundlers also understand
+// this shape.
+import pkg from '../package.json' with { type: 'json' };
 export const VERSION = pkg.version;