Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow tests to tamper with Node.js built-ins without breaking AVA

See original GitHub issue

With latest master (c01ac05ef610c87f5c264b1a3eb80f89b4fc0832) and Node.js 4 and 7.

import fs from 'fs';
import test from 'ava';
import sinon from 'sinon';

test(t => {
	fs.readFileSync = sinon.stub(fs, 'readFileSync');
	// ...
	fs.readFileSync.restore();
	t.pass();
});

  2 exceptions

  Uncaught Exception
  TypeError: Cannot read property 'sections' of undefined
    new SourceMapConsumer (/Users/sindresorhus/dev/ava/node_modules/source-map/lib/source-map-consumer.js:20:19)
    mapSourcePosition (/Users/sindresorhus/dev/ava/node_modules/source-map-support/source-map-support.js:171:14)
    wrapCallSite (/Users/sindresorhus/dev/ava/node_modules/source-map-support/source-map-support.js:338:20)
    /Users/sindresorhus/dev/ava/node_modules/source-map-support/source-map-support.js:373:26
    Function.prepareStackTrace (/Users/sindresorhus/dev/ava/node_modules/source-map-support/source-map-support.js:372:24)

  ✖ Test results were not received from test.js

I think we need to protect all builtins from being overridden, so mocking in the tests doesn’t affect our usage or our dependencies’ usage of core APIs. Maybe running the test files in a new vm context would help with that?

There is a $60.00 open bounty on this issue. Add more on Issuehunt.

Checkout the Issuehunt explorer to discover more funded issues.

Need some help from other developers? Add your repositories on Issuehunt to raise funds.