`npm run build` creates large index.js file - requesting to ignore this in file limitations
Lastraum K
Downloaded a builder scene of 3.7mb with barely any glb assets. Ran
npm run build
and saw the index.js
file became 4.2mb.I have noticed this on other scenes as well. Additionally, it looks like
.tsx
files increase the total index.js
file size.To my knowledge, this
index.js
file size counts towards a scenes file limitations. Can we disregard the
index.js
in the scene size limitations?Ozymandias
npm run build -- -p
should yield a much more palatable result.If I remember correctly,
npm run deploy
does the -p
under the hood, but I haven't checked lately, I actually use my own process which includes npm run deploy -- --skip-build
.Lastraum K
Ozymandias appreciate the reply! the flag
-p
does reduce the index.js
file size by about 50%. This is a great step forward! However; for custom scenes, like ours, the index.js
went from 11mb to 6.1mb. That additional 6.1mb counting towards your parcel limit is still a hindrance.Lean Mendoza
Ozymandias
Yes,
npm run deploy
includes the -p (--production) parameter before uploading it.Lastraum K
Lean Mendoza thanks! still would like to regain that 6.1mb "counted" to your scene limitations.