/opt/canhelp/node_modules/next/dist/server/node-environment-extensions
NameSizeModeActions
console-dev.d.ts110644editdlrm
console-dev.js63110644editdlrm
console-dev.js.map92550644editdlrm
date.d.ts110644editdlrm
date.js23590644editdlrm
date.js.map34880644editdlrm
error-inspect.d.ts110644editdlrm
error-inspect.js2520644editdlrm
error-inspect.js.map3610644editdlrm
node-crypto.d.ts4810644editdlrm
node-crypto.js56030644editdlrm
node-crypto.js.map81260644editdlrm
random.d.ts4470644editdlrm
random.js12280644editdlrm
random.js.map17400644editdlrm
utils.d.ts1250644editdlrm
utils.js67850644editdlrm
utils.js.map81330644editdlrm
web-crypto.d.ts4800644editdlrm
web-crypto.js19190644editdlrm
web-crypto.js.map29420644editdlrm
Edit: /opt/canhelp/node_modules/next/dist/server/node-environment-extensions/random.js (1228B)
/** * 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. */ "use strict"; Object.defineProperty(exports, "__esModule", { value: true }); const _utils = require("./utils"); const expression = '`Math.random()`'; try { const _random = Math.random; Math.random = (function random() { (0, _utils.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