Difference between just modifying Path

[rtgibbons]

I just ran across this plugin when searching for how to do this on a current project.

I'm curious as to what the difference is between this and just modify the paths config object?

require.config({
  paths : {
    'components/component1': 'components/component1.abcd1234',
    'components/component2': 'components/component2.efgh5678',
  }
});

Looks like either way main.js is going to have be modified after the fingerprinting of the files has been performed with the fingerprint? And a bonus of doing this, we don't have to modify the define's in our existing project?

(Please note, I'm a DevOps guy with backend focus, my knowledge of requriejs is limited, so feel free to point out any flaw I might have, or ask for more clarification if I skipped over something)

[meinaart]

If you have a different fingerprint for every file then that approach is more or less the same ;). I developed it for an environment where we used one fingerprint for every release.

In the end I didn't even use my own plugin that much because we switched to fingerprinting the whole directory and just changed the basePath.

It's still useful if you don't want to give all resources their own unique fingerprint.

If you have a specific wish just let me know. I could also add matching the file name with a regex for example.

If every file has their own unique fingerprint I would choose the path generation approach. Saves you from adding "fingerprint!" with every require call. That's also more readable and friendlier for other developers.

I now only use my plugin for fingerprinting dynamically loaded CSS files.