Socket
Socket
Sign inDemoInstall

@gltf-transform/core

Package Overview
Dependencies
Maintainers
1
Versions
205
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@gltf-transform/core - npm Package Compare versions

Comparing version 3.7.2 to 3.7.3

4

package.json
{
"name": "@gltf-transform/core",
"version": "3.7.2",
"version": "3.7.3",
"repository": "github:donmccurdy/glTF-Transform",

@@ -55,3 +55,3 @@ "homepage": "https://gltf-transform.dev/",

},
"gitHead": "4bc686d4b1c3c4acfa3cc7fdffc7c2b563835d7a"
"gitHead": "8a8e6c1c1c86b261d1b99dda068c051b21a6cb50"
}

@@ -162,4 +162,6 @@ import { Format } from '../constants.js';

}
// TODO(v4): Consider storing decoded URIs in memory, and avoid decoding here. However,
// we'll need to think through implications for absolute URLs.
const resource = Buffer.from(resources[resourceURI]);
const resourcePath = path.join(dir, resourceURI);
const resourcePath = path.join(dir, decodeURIComponent(resourceURI));
await fs.mkdir(path.dirname(resourcePath), { recursive: true });

@@ -166,0 +168,0 @@ await fs.writeFile(resourcePath, resource);

@@ -191,5 +191,8 @@ import { Format, GLB_BUFFER, VertexLayout } from '../constants.js';

// TODO(v4): Perhaps the resources dictionary could have been keyed by decoded URIs
// like "my image.png" instead of "my%20image.png". But for now, we use the URIs
// verbatim as found in resource definition. Consider revisiting in v4.
jsonDoc.resources[uri] = await this.readURI(this.resolve(base, uri), 'view');
this.lastReadBytes += jsonDoc.resources[uri].byteLength;
}
},
);

@@ -196,0 +199,0 @@ await Promise.all(pendingResources);

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is too big to display

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc