Good or bad idea to check the cache into source control?

[trusktr]

Could checking the cache into source control mean fast builds when deploying to new machines? Or is that a bad idea?

[mzgoddard]

This is something I'd like to support but it's a long way outprobably not going to happen. The biggest issue right now is the full file paths in the different parts cache information. Iirc its not just hard-source but also the records.json part from webpack core. You could check in the cache but any new systems would have to clone to the exact file path of what was checked in. The next issue would be system idiosyncrasies will be hard to detect between different machines.

One use case that is currently supported is storing caching for Continuous Integration where those two listed problems above are very unlikely.

[MattSurabian]

Ah true, webpack resolves the absolute paths so unless your other machine had the exact directory structure stuff would break.

There's also the logistical issue of commit noise.

[trusktr]

Ah, interesting. In my case I develop in a VM that is the exact same as the prod machines, with the exact same paths. I put this on pause as I started randomly getting an error that I will come back around to debug.

…

On Mar 29, 2017 12:54 PM, "Matthew Surabian" ***@***.***> wrote: Ah true, webpack resolves the absolute paths so unless your other machine had the exact directory structure stuff would break. There's also the logistical issue of commit noise. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#118 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASKzmx2Yd4mTw0KCTDc11v9URGT21Psks5rqrblgaJpZM4MtXx2> .