Decreasing Three.js repo size
See original GitHub issueDescription of the problem
-
Since we have screenshots they polluting github repo. Every new commit that changes screenshot increasing overall repo size. Probably exists a way how to decrease it in future with
.gitattributes && git lfs
. Any suggestions? -
Somebody complain that
puppeteer
is too big. But who installs full three.js from git? Only three.js contributes? This is a problem?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to reduce bundle size with Webpack? - three.js forum
Check out this starter three. js project for more details. The final build size is of the bundle is 604 KB.
Read more >reduce bundle size for three js · Discussion #812 - GitHub
So after doing webpack analysis I found out that threejs is taking most of the space. Three.module.js. Stat Size : 1.23 MB Parsed...
Read more >Reducing bundle-size | React Three Fiber
This way you can reduce it to 80-50kb, or perhaps less, depending on what you need.
Read more >Unable to reduce the size of the custom 3D model in three-js ...
Contribute to zappar-xr/threejs-example-face-tracking-3d-model development by creating an account on GitHub. Although, I am able to get it ...
Read more >Three.js: ways to reduce file size of models? - Stack Overflow
Why not just load the .obj file into three. · I only do this because the editor is quite convenient for applying the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s fair to note that the repo size can be an issue for people with slow speed or small data caps.
However, I think the conclusion in #6922 is still OK. There’s an extra 70mb added due to these screenshots which I don’t think is a big deal since it’s a one time download.
Note the comment from @bhouston suggesting you do shallow clone if repo size is an issue.
Looking at the last couple of weeks, it does not seem this happens quite often.
In any event, I don’t think the repo size is an issue. It’s mostly relevant to devs and you normally clone the repo only once per device. And let’s not forget shallow clones.