Impossible to rerun in the same runtime because of require cache

[soswow]

Impossible to rerun in the same runtime because of require cache

[amavisca]

I don't mind the idea of invalidating the cache. I think the alternative is to manually run code in a vm context. It's nice being able to offload the effort of execution to require.

If you'd like you could submit your cache invalidation + specs for it as a PR - otherwise I can add a fix to this.

[amavisca]

A problem with invalidating the cache is that this will only really the problem with your spec files. If your source files change and are being require'd into your spec, you won't see a change in your source file within the same process because that file is still cached.

What wasn't working for you with spawning a new process?

[soswow]

I was using it with web driver. And i keep webdriver client reference to
speedup execution time.

On Tue, 3 Mar 2015 07:27 Christopher Amavisca [email protected]
wrote:

A problem with invalidating the cache is that this will only really the
problem with your spec files. If your source files change and are being
require'd into your spec, you won't see a change in your source file
within the same process because that file is still cached.

What wasn't working for you with spawning a new process?

—
Reply to this email directly or view it on GitHub
#30 (comment).

[slackersoft]

I think if we get to a point where jasmine-npm has some ability to watch the project and run specs when files change, we will still need to spawn a child process to actually run the specs, given all of the issues around require caching.

Other workarounds would involve loading all of the code up into a vm that had a fresh cache each time, but that would probably still break your use case.

I've made some notes in #5 about making sure that new code is loaded and probably forking a child process to get a fresh cache. I'm going to close this in favor of that issue, since it seems like this has mostly morphed into that issue.

Thanks for using jasmine!