/opt/canhelp/node_modules/next/dist/esm/server/node-environment-extensions
NameSizeModeActions
console-dev.js61470644editdlrm
console-dev.js.map92710644editdlrm
date.js22370644editdlrm
date.js.map34720644editdlrm
error-inspect.js1510644editdlrm
error-inspect.js.map3690644editdlrm
node-crypto.js54330644editdlrm
node-crypto.js.map80690644editdlrm
random.js11300644editdlrm
random.js.map17450644editdlrm
utils.js64750644editdlrm
utils.js.map81610644editdlrm
web-crypto.js18090644editdlrm
web-crypto.js.map29360644editdlrm
Edit: /opt/canhelp/node_modules/next/dist/esm/server/node-environment-extensions/random.js (1130B)
/** * We extend Math.random() during builds and revalidates to ensure that prerenders don't observe randomness * When cacheComponents is enabled. randomness is a form of IO even though it resolves synchronously. When cacheComponents is * enabled we need to ensure that randomness is excluded from prerenders. * * The extensions here never error nor alter the random generation itself and thus should be transparent to callers. */ import { io } from './utils'; const expression = '`Math.random()`'; try { const _random = Math.random; Math.random = (function random() { io(expression, 'random'); return _random.apply(null, arguments); // We bind here to alter the `toString` printing to match `Math.random`'s native `toString`. // eslint-disable-next-line no-extra-bind }).bind(null); Object.defineProperty(Math.random, 'name', { value: 'random' }); } catch { console.error(`Failed to install ${expression} extension. When using \`experimental.cacheComponents\` calling this function will not correctly trigger dynamic behavior.`); } //# sourceMappingURL=random.js.map