mirror of
https://github.com/nodejs/node.git
synced 2024-11-29 23:16:30 +01:00
caee112e52
There is actually no reason to use `assert.doesNotThrow()` in the tests. If a test throws, just let the error bubble up right away instead of first catching it and then rethrowing it. PR-URL: https://github.com/nodejs/node/pull/18669 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
16 lines
402 B
JavaScript
16 lines
402 B
JavaScript
'use strict';
|
|
require('../common');
|
|
const vm = require('vm');
|
|
|
|
// Check that we do not accidentally query attributes.
|
|
// Issue: https://github.com/nodejs/node/issues/11902
|
|
const handler = {
|
|
getOwnPropertyDescriptor: (target, prop) => {
|
|
throw new Error('whoops');
|
|
}
|
|
};
|
|
const sandbox = new Proxy({ foo: 'bar' }, handler);
|
|
const context = vm.createContext(sandbox);
|
|
|
|
vm.runInContext('', context);
|