Angular Tree Shaking

Questions
1

Has anyone gotten tree-shaking to work when building an Angular app with @babylonjs/core? I am getting a build size (via source-map-explorer) for @babylonjs/core of 3.74MB, but the same exact code in a Vite build is giving me under 2MB total. I have module set to ES2022 in my ts.config and optimization set to true in angular.json. Here are the imports from the only file that imports BJS

import { Scene } from "@babylonjs/core/scene"
import "@babylonjs/core/Helpers/sceneHelpers";
import { SceneLoader } from "@babylonjs/core/Loading/sceneLoader";
import { AssetContainer } from "@babylonjs/core/assetContainer";

import "@babylonjs/loaders/glTF/2.0/glTFLoader";
import "@babylonjs/loaders/glTF/2.0/Extensions/KHR_draco_mesh_compression";
import "@babylonjs/loaders/glTF/2.0/Extensions/KHR_materials_pbrSpecularGlossiness";
import "@babylonjs/loaders/glTF/2.0/Extensions/KHR_texture_transform";
import "@babylonjs/loaders/glTF/2.0/Extensions/KHR_mesh_quantization";```
2

Is it possible angular doesn’t minify? Or add sourcemaps to the .js file directly?

I am now sure how angular’s build system is configured, but if it’s not some dev-overhead, it must be something there