Skip to content

issues Search Results · repo:IanVS/vitest-fetch-mock language:TypeScript

Filter by

17 results
 (56 ms)

17 results

inIanVS/vitest-fetch-mock (press backspace or delete to remove)

I m using vitest-fetch-mock in our backend tests, but it is throwing this error ReferenceError: window is not defined at resolveInput (file:///root/app/node_modules/.pnpm/vitest-fetch-mock@0.4.3_vitest@3.0.6_@types+node@22.13.5_/node_modules/vitest-fetch-mock/src/index.ts:327:3) ...
  • sibelius
  • 1
  • Opened 
    11 days ago
  • #41

The following example from the readme does not work as expected (and as before v0.4): Image Adding this simple test to the api.test.ts suite shows that: it.only( does not mock by default , () = { ...
  • kaisermann
  • 1
  • Opened 
    22 days ago
  • #40

Running npm run build on my project fire many of those errors: src/stores/__tests__/pin.spec.ts:72:20 - error TS2339: Property requests does not exist on type { (input: URL | RequestInfo, init?: RequestInit ...
needs reproduction
  • Daniele-Tentoni
  • 2
  • Opened 
    on Jan 20
  • #39

I m encountering the following warning when running Vitest: Sourcemap for .../node_modules/vitest-fetch-mock/dist/index.js points to missing source files Look at what is distributed to NPM (as of version ...
  • joealden
  • 9
  • Opened 
    on Jan 15
  • #38

I need to mock a fetch call, which returns a pdf. Not sure who to do that. I ve already tried some stuff like: fetchMocker.mockResponseOnce(await readFile(path));
  • Mese1953
  • 1
  • Opened 
    on Dec 17, 2024
  • #37

The DOMException is thrown, but without a name. This does not comply the API definition here: https://developer.mozilla.org/en-US/docs/Web/API/AbortController/abort
  • naymic
  • 2
  • Opened 
    on Nov 25, 2024
  • #35

We should take a look at @fetch-mock/vitest, and if it s functionally similar, perhaps we can sunset this project and point folks over there.
  • IanVS
  • 1
  • Opened 
    on Nov 7, 2024
  • #33

I was on 0.3.0 with everything working as expected. 0.4.0 caused issues with fetchMock not available on the global context so I jumped to 0.4.1, but now none of the fetch calls are getting mocked and just ...
  • morleytatro
  • 8
  • Opened 
    on Oct 31, 2024
  • #32

I might not have properly analyzed this, but version 0.4.1 is not working in a couple of projects and I think it comes down to handling of relative URLs. My projects run in a Web / Web extension context ...
  • birtles
  • 6
  • Opened 
    on Oct 30, 2024
  • #31

Hello again, I m still on the upgrade-path from 0.3.0 to 0.4.x. In some tests I was asserting the request-body to ensure it matches the API-Requirements: const fetchRequests = fetchMock.requests(); ...
  • DotCoyote
  • 3
  • Opened 
    on Oct 29, 2024
  • #30
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub