{"version":"2.1.248","anchor":"the-same-wrapper-removal-seen-in-the-spinner-word-list","canonical_anchor":"the-same-wrapper-removal-seen-in-the-spinner-word-list","heading":"The same wrapper removal, seen in the spinner word list","tier":"internal","area":"Bundling","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/the-same-wrapper-removal-seen-in-the-spinner-word-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### The same wrapper removal, seen in the spinner word list\n\nThe same load-time change is visible in the spinner word list; behaviour is unchanged.\n\n**What**\n\nThe bundler's lazy per-module wrappers are gone, so module-scope side effects run at load rather than on first use. The spinner verb list, for example, sat inside a closure in the previous build and is a bare top-level array here. Timing changes, behaviour does not.\n\n**Details**\n\n- Not gated; this is the shape of the build itself.\n- Also fixes the order in which module-scope state is created, since it no longer depends on who imports what first.\n\n**Evidence**\n\n`\"Zigzagging\"`\n\n- Area: Bundling\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}