Vite/Rollup 'failed to resolve import "@babylonjs/core/Meshes/gaussianSplattingMesh"': Babylon.js 9 keeps it under Meshes/GaussianSplatting/, and the barrel import is an 8.3 MB chunk
Symptom: adding Babylon.js as an alternative Gaussian splat renderer (next to three.js + gaussian-splats-3d) in a Vite 6 app, with import { GaussianSplattingMesh } from '@babylonjs/core/Meshes/gaussianSplattingMesh', makes vite build fail with [vite]: Rollup failed to resolve import "@babylonjs/core/Meshes/gaussianSplattingMesh" from "/app/main.js". This is most likely unintended because it can break your application at runtime. If you do want to externalize this module explicitly add it to build.rollupOptions.external.
Cause: the path is wrong. In @babylonjs/core 9.36.0 the file is Meshes/GaussianSplatting/gaussianSplattingMesh.js (alongside gaussianSplattingMeshBase.js and .pure.js variants). @babylonjs/core has no exports map, so deep imports resolve purely by file path, and a missing folder level fails at build time.
What works:
// deep import (keeps the bundle smaller than the barrel)
import { GaussianSplattingMesh } from '@babylonjs/core/Meshes/GaussianSplatting/gaussianSplattingMesh';
// or the barrel (simplest, but pulls in the whole engine)
import { GaussianSplattingMesh } from '@babylonjs/core';To list what the package actually exports: node -e "import('@babylonjs/core').then(m => console.log(Object.keys(m).filter(k => k.includes('Gaussian'))))". On 9.36.0 that prints GaussianSplattingMesh, GaussianSplattingMeshBase, GaussianSplattingMaterial, GaussianSplattingGpuSorter and more.
Size trap: with the barrel import, Vite's babylon chunk was 8,316 KB (1,877 KB gzipped). Together with playcanvas (7.6 MB) and spark (2.8 MB) in one build, npm run build inside a node:22-slim container died with exit status 134 (out of memory). Options that worked: lazy-load each renderer with await import('./babylon-loader.js') plus build.rollupOptions.output.manualChunks, raise the heap with NODE_OPTIONS=--max-old-space-size=4096, or keep Babylon out of the bundle and load https://cdn.babylonjs.com/babylon.js with a script tag at runtime (window.BABYLON). Careful: adding '@babylonjs/core' to rollupOptions.external while still writing import ... from '@babylonjs/core' leaves a bare specifier the browser can't resolve, so pair external with the CDN global or an import map.