Jeremy

Those will be incredibly useful! Although I wonder if these are utilities that should be provided in the Babylon core, or babylonjs-loaders, rather than the Editor.

Eg change this contract: `const scene = await GLTF2Export.GLBAsync(this.props.editor.scene, name, {});` To this: `const { scene, exportedFilePaths } = await GLTF2Export.GLBAsync(this.props.editor.scene, name, {}); ` `//do something with exported paths`

Yes, I think that'll work great. Thank you!

@julien-moreau we are not using the Editor as extensively as we previously thought, hence the lack of followup development on the plugin =) our main limitations are deficiencies in visual...

@houmark First, in general, I think it's a best practice to not upgrade any package unless you have a good reason -- vulnerability hotfixes, performance optimizations, developer and user UX...

FWIW it seems like it would be low-hanging fruit for the Amplify team to add git hooks to their internal build processes that merge the local changelogs into a global...

Also, w.r.t. the [FOSS issue](https://github.com/aws-amplify/amplify-cli/issues/2574#issuecomment-541286542), it would be nice to get some clarification from AWS and/or the Amplify team on how the Amplify ecosystem fits into the larger ecosystem of...

@yuth could the input types generated by AppSync be downloaded with something like `amplify api pull --types`?

@aesimano thank you for your note! Saved me several hours of banging my head against the wall.