Three.js: Decreasing Three.js repo size

[munsocket]

Description of the problem

1) 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?

2) Somebody complain that puppeteer is too big. But who installs full three.js from git? Only three.js contributes? This is a problem?

[makc]

@munrocket we had this talk 5 years ago #6922 they said no.

[munsocket]

I am agree but in current situation with screenshots in repo it can increase much faster, so probably somebody know some solution.

[Mugen87]

Every new commit that changes screenshot increasing overall repo size.

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.

[finnbear]

Consider downloading the npm package (https://www.npmjs.com/package/three) which has everything you need for production purposes at only 21MB.

[looeee]

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.

[munsocket]

Looks like this is cool git feature:

git clone --depth 1 <url>

I will close this issue, if you have any complains please just open a new one.