You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 5, 2020. It is now read-only.
Currently, buster-coffee only works with Buster.JS's browser testing, and not Buster.JS's Node.js testing. This is because buster-coffee just keeps the compiled JS sources in memory, while require() in Node.js apps expect to find the required modules on disk.
A possible solution is to create a "nodevm" test runner in Buster.JS, which run the tests in an environment controlled by the Node.js vm module. This gives the test runner control of the global namespace. Thus, it can override require() with a custom implementation that can access in-memory JS resources.
The text was updated successfully, but these errors were encountered:
Currently, buster-coffee only works with Buster.JS's browser testing, and not Buster.JS's Node.js testing. This is because buster-coffee just keeps the compiled JS sources in memory, while
require()
in Node.js apps expect to find the required modules on disk.A possible solution is to create a "nodevm" test runner in Buster.JS, which run the tests in an environment controlled by the Node.js vm module. This gives the test runner control of the global namespace. Thus, it can override
require()
with a custom implementation that can access in-memory JS resources.The text was updated successfully, but these errors were encountered: