bundle exec rake assets:precompile is compiling all assets (but only every time another OS is compiling them)

[h0jeZvgoxFepBQ2C]

Our team has a big problem and we tried multiple countermeasures, but we couldn't find any solution.

Due to server and system constraints, we precompile our assets (sprockets + webpacker) before releasing new versions.

The normal rails script RAILS_ENV=production bundle exec rake assets:precompile is working fine and compiles only the last changed files - except if someone of my team is compiling them also.

We are syncing all code changes before with git, we run yarn install --check-files before each compilation to ensure we have the same npm packages. But it still doesn't work as expected.

When I compile only on my machine, only new assets get compiled. When another teammate compiles them (with pulled changes, updated manifest files,...), all assets get precompiled. If they compile again only on their machine, only the latest changed files are precompiled again.

I'm on OSX, my mates are on Linux/Ubuntu.

Does anyone have a suggestion on how to fix this issue? Or do I miss something? My question is mostly about webpacker, sprockets looks fine.

Also it seems that only some small webpack internal numbers are incresed, see following screenshow:

Node: v.14.9.0
Yarn: 1.22.5

[Aeon]

@h0jeZvgoxFepBQ2C look into the files tmp/cache/webpacker/last-compilation-digest-development, tmp/cache/webpacker/last-compilation-digest-production, etc.

Implementation details in https://github.com/rails/webpacker/blob/master/lib/webpacker/compiler.rb - the fresh? check uses this file at each run to determine whether recompilation is needed

[justin808]

We've got some other issues that concern this.

Due to server and system constraints, we precompile our assets (sprockets + webpacker) before releasing new versions.

that's normal.

Please reopen if you have more details.