{"version":"2.1.221","anchor":"large-amount-of-module-initializer-churn-with-no-visible-beh","canonical_anchor":"large-amount-of-module-initializer-churn-with-no-visible-beh","heading":"Large amount of module-initializer churn with no visible behaviour","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/large-amount-of-module-initializer-churn-with-no-visible-beh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Large amount of module-initializer churn with no visible behaviour\n\nDozens of module-loading tweaks shuffled around internally with no effect you can see.\n\n**What**\n\nAbout forty changes in this build are single added or removed initializer calls at the top of lazily-evaluated module bodies.\n\n**Details**\n\n- Mostly extra dependency modules pulled in, with a couple dropped.\n- A handful of one-line function bodies pair up differently between builds purely because of minified-name reassignment.\n- No user-visible behaviour could be attributed to any of them individually; they are consistent with dependency-graph reshuffling caused by the other changes here.\n\n**Evidence**\n\n`iDp = require(\"crypto\");`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}