gltf-pipeline as an npm module?

[ptrgags]

@ebogo1 this is related to #9473

Today I updated gltf-pipeline, and noticed that the way we add the changes to Cesium are:

1. run npm build-cesium in gltf-pipeline (Not sure everything this build step does, but it does take some Node.js code involving Buffer and adapts it for the browser according to @lilleyse )
2. copy the output files into Source/ThirdParty/GltfPipeline
3. commit the changes

Could this workflow be changed to use npm instead? e.g. release gltf-pipeline and then npm install in cesium?

[lilleyse]

Not sure everything this build step does, but it does take some Node.js code involving Buffer and adapts it for the browser according to @lilleyse

It's actually simpler than that. It only packages certain files that are needed in CesiumJS and skips files that use Buffer and other Node concepts. So there's no browserify or rollup going on. That's a separate discussion: CesiumGS/gltf-pipeline#332.