Cache isn't invalidated if transform options are changed about browserify-incremental HOT 6 OPEN

To fix this, environment and configuration need to become part of the cache key (which we should have always been doing 😬). This is not yet implemented, but it's my first priority.

from browserify-incremental.

Awesome! Can you clarify what parts of the environment and configuration would become part of the cache key?

I've got around the issue for now by not using browserify-incremental for "prod" builds at all.

from browserify-incremental.

Basically when items are stored in the cache, currently they are keyed by file name only. If that key also included a digest of things like the node env and browserify opts, then when those things change, that cache entry wouldn't be used.

from browserify-incremental.

Would it work to mark the NODE_ENV in the browserify incremental cache? Like cacheFile: './browserify-cache-' + NODE_ENV + '.json' roughly?

from browserify-incremental.

Won't help with changes to transformation or plugin settings in package.json or the browserify command line, @aquach. @jsdf' approach of invalidating if the config changes makes sense.

from browserify-incremental.

maybe it could make a json of the options, make a base64 sha1 hash out of that string and append that to the cache file name? that way the cache file would match the same (and only the same) options.

The cli could do the same technique with it is command line argument string.

from browserify-incremental.