Remove the manifest data from cache on crx.load()

[binhqx]

The require API keeps a global cache of all the files loaded via require(). Changes in the 'manifest.json' will not be picked up after the first time crx.load(...) is run.

[ngyikp]

How about JSON.parse(fs.readFileSync()) [or the async version] instead of require()?

[thom4parisot]

Just out of curiosity, in which case would crx run and encounter the same manifest twice; a manifest which would have been modified in the meantime?

In any case, I totally agree this kind of side effect should be avoided and I'd rather rely an fs.readFile call instead. I suspect it is more nicely browserified too (if it has to).