Open wizzard0 opened 4 years ago
oh yeah i noticed this the other day, I don't think it was always happening I think something in Next might have changed recently...
Btw, FABs should only ever have the assets for the current version of the code, but when they're deployed they only ever add files to the _assets
directory, so all previous versions should still be fine to run.
That's not currently implemented perfectly actually, have raised #170 to remind myself to finish that off.
@wizzard0, where all of these builds locally? Next won't clean out the .next
folder, so if you run a bunch of them on the command line and then build, you would get all the assets. If you remove the .next
directly before a build, you should have a clean build.
e.g. after about 10 builds:
this is not a bug per se, it is needed, so that asset deployment is zero-downtime (if half of the assets were served with new version, and half with old); AND this is likely more of a nextjs\webpack issue, but it might make sense to dedup the assets by md5/sha256, and/or keep "last 2-3 versions" in the future