Can this plugin bundle assets pointed to by glTF JSON files?

[krispya]

I have been using GLB files in dev mostly, but I recently wanted to start using glTF JSON with separated textures and bin so that I could reuse textures more easily. However, I ran into the Vite bundling problem where the imported glTF file gets bundled but none of the assets it points to. Can this Vite plugin handle that without transforming the file to GLB?

PS: I did not see a discussion tab for this repo or I would have posted this there.

[donmccurdy]

Defined here ...

rd-bundler-3d-plugins/packages/core/core.js

Lines 127 to 137 in 880238c

	const publicAssetPath = publicPath + "/" + `${basename}.glb`;
	const outputAssetPath = path.join(outputPath, `${basename}.glb`);
	const document = await io.readJSON({ json, resources });
	await document.setLogger(logger).transform(...pluginOptions.transforms);
	this.emitFile({
	type: "asset",
	fileName: outputAssetPath,
	source: await io.writeBinary(document),
	});

... this plugin does always bundle input files to .glb, embedding any binary or image resources they depend on. I don't know of any reason it would have to work that way, but note that to support the 'hash' suffix properly, we'd need to append a hash to these resource filenames and update references from the .gltf.

[krispya]

I see! I do some pre-processing with gltf-transform but I'd like to do some post-processing with this plugin as well for builds. But the most basic expectation I have is that any .glb, .gltf and its linked assets inside of /src properly make it into a build. Does that align with the vision for this plugin?

[donmccurdy]

Nothing is lost now, but your linked resources (.png, .jpg, .bin, ...) are getting embedded into .glb files in the bundling step. I think changing that so it's possible to output .gltf files — keeping external resources external — in the bundle would be within the vision of this plugin from my perspective, but isn't something I have bandwidth to work on right now. PRs would be welcome though!