Do not use global cache

[mxl]

Currently when running css-modulesify first time passed postcss plugins are cached in loader and the subsequent runs in the same process but with different set of plugins result in using cached plugins. The only workaround is to reload module with delete require.cache[require.resolve('css-modulesify')];.

This is happening because of persisting cache globally that was made because cache option passed to browserify is forwarded to module-deps where it's filled with record for each module (record for css module contains javascript code generated with cmify.js). So without persisting tokens and loader between runs when using browserify cache option (e.g. with rebundler) if css file is not changed then file record is not removed from browserify cache and module-deps does not reapply transformations and css (which is "side-effect" of transformations) is not outputted which was the #32 issue reported by @joeybaker and was fixed by him in #40 by introducing global cache.

Persisting cache globally results in issue like I described above and I suggest to use cache option that can be reused between runs. So it makes css-modulesify stateless again but allows to persist cache e.g. for using with rebundler.

[joshwnj]

Thanks @mxl ! What you've described sounds good. I'll take a look and then we should be good to go ahead and merge.

[joshwnj]

published to npm v0.28.0