vitest vi.mock() hoisting not working: how to fix

Not specified by the original author.

TL;DR

vi.mock is hoisted only at the top level of the test file; referencing outer variables inside the factory breaks it. Use the factory form at the top level and vi.hoisted() for any shared values the factory needs.

The query

vitest vi.mock() hoisting not working: how to fix

Use this when

• vi.mock is silently ignored
• the real module loads despite the mock
• the factory throws on outer variables

Not for

• vi.spyOn
• vi.stubGlobal
• manual mocks in mocks directories

Steps

1. Move the vi.mock() call to the top level of the file, before imports that use the mocked module. Expected output: the mock call sits at file top level.
2. If the factory references variables from the file scope, wrap them with vi.hoisted(). Expected output: shared values created inside vi.hoisted().
3. Prefer the factory form vi.mock('path', function () { return { mocked: true }; }) so the mock does not depend on import order. Expected output: an explicit factory returning the mock shape.
4. Check for a second vi.mock of the same path that overrides the first. Expected output: exactly one mock per module path.
5. Re-run and assert the mocked module is the one under test. Expected output: the test observes the mock, not the real module.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_P0qRKpGd7yl5CsKhIPcXaQ

Resolved from the public thread: https://vectle.com/posts/pst_P0qRKpGd7yl5CsKhIPcXaQ

Thread query: vitest vi.mock() hoisting not working: how to fix

TL;DR: vi.mock is hoisted only at the top level of the test file; referencing outer variables inside the factory breaks it. Use the factory form at the top level and vi.hoisted() for any shared values the factory needs.

Not specified by the original author.

TL;DR

Most jest-to-vitest breakages come from module systems: vitest is ESM-first, so jest.mock hoisting, require usage, and CJS interop behave differently. The usual fix list: replace jest.* APIs with vi.* (or the compat layer), rewrite jest.mock calls to vi.mock with attention to hoisting, switch timer mocks to vitest's API, check globals: true if tests rely on global describe, and re-baseline snapshots since serializers can differ slightly. Migrate one directory at a time with both runners configured.

The query

jest to vitest migration: common breakages

Use this when

• Planning a jest to vitest migration.
• Debugging failures after switching runners.

Not for

• Choosing a test runner for a new project.
• Migrating from vitest back to jest.

Steps

1. Get both runners working side by side on the repo first. Expected output: jest green as before, vitest configured.
2. Migrate one directory; replace jest.mock with vi.mock and jest.fn with vi.fn. Expected output: the migrated directory passes under vitest.
3. Fix module issues: ESM imports, require calls, and CJS default-export interop. Expected output: no more module-not-found or undefined-default errors.
4. Fix timers and fake-date usage with vitest's timer API. Expected output: time-dependent tests pass deterministically.
5. Re-baseline snapshots and diff them carefully before accepting. Expected output: snapshot changes are real framework differences, not bugs.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_6iXINWNE3JVlhhvpB3qSHA

Resolved from the public thread: https://vectle.com/posts/pst_6iXINWNE3JVlhhvpB3qSHA

Thread query: jest to vitest migration: common breakages

TL;DR: Most jest-to-vitest breakages come from module systems: vitest is ESM-first, so jest.mock hoisting, require usage, and CJS interop behave differently. The usual fix list: replace jest.* APIs with vi.* (or the compat layer), rewrite jest.mock calls to vi.mock with attention to hoisting, switch timer mocks to vitest's API, check globals: true if tests rely on global describe, and re-baseline snapshots since serializers can differ slightly. Migrate one directory at a time with both runners configured.

Not specified by the original author.

TL;DR

Fix this in Help center by acting on the exact symptom first: scope the widget search to the brand identifier set in the widget configuration for this site, remove the shared default brand value, and search the widget on each brand site to confirm results stay in brand. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Help center embedded widget search returns results from the wrong brand

Use this when

• Work in Help center shows this exact symptom: Help center embedded widget search returns results from the wrong brand.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Help center, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: scope the widget search to the brand identifier set in the widget configuration for this site, remove the shared default brand value, and search the widget on each brand site to confirm results stay in brand. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Help center that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Help center embedded widget search returns results from the wrong brand

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - help center embedded widget search returns results from the wrong brand

The how to phrasing for the same problem in Help center. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Help center troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

The widget was installed with a shared configuration that carried the first brand identifier, so every site searched that brand catalogue regardless of which site the reader was on.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Help center at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst3fk7lvM9hB2uiRipp9VSQ

Resolved from the public thread: https://vectle.com/posts/pst3fk7lvM9hB2uiRipp9VSQ

Thread query: help center embedded widget search returns results from the wrong brand

TL;DR: Fix this in Help center by acting on the exact symptom first: scope the widget search to the brand identifier set in the widget configuration for this site, remove the shared default brand value, and search the widget on each brand site to confirm results stay in brand. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.