npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

google-maps-vitest-mocks

v1.0.7

Published

Vitest mocks for google maps

Downloads

5

Readme

Google maps vitest mocks

⚡️ Easy to use vitest mocks for google maps. This is a rewrite of @googlemaps/js-jest-mocks, meant to be used with vitest instead of jest.

Getting started

Installation and usage

With npm:

$ npm i --save-dev google-maps-vitest-mocks
# or
$ yarn add -D  google-maps-vitest-mocks

Usage

This package has been designed to be used as @googlemaps/js-jest-mocks.

Inspecting mocks

You can inspect what happens with the created mock instances (e.g. Map or Marker) via the mockInstances object.

import {
  initialize,
  Map,
  Marker,
  mockInstances,
} from "google-maps-vitest-mocks";
import { beforeEach, test, expect } from "vitest";

beforeEach(() => {
  initialize();
});

test("my test", () => {
  const map = new google.maps.Map(null);
  const markerOne = new google.maps.Marker();
  const markerTwo = new google.maps.Marker();

  map.setHeading(8);
  markerOne.setMap(map);
  markerTwo.setLabel("My marker");

  const mapMocks = mockInstances.get(Map);
  const markerMocks = mockInstances.get(Marker);

  expect(mapMocks).toHaveLength(1);
  expect(markerMocks).toHaveLength(2);
  expect(mapMocks[0].setHeading).toHaveBeenCalledWith(8);
  expect(markerMocks[0].setMap).toHaveBeenCalledTimes(1);
  expect(markerMocks[1].setLabel).toHaveBeenCalledWith("My marker");
});

Cleaning up mocks

Whenever initialize() is called, the captured mocks are automatically cleaned. Using any of Jest's methods, you can clean the mock instances at any time:

import {
  initialize,
  Map,
  Marker,
  mockInstances,
} from "google-maps-vitest-mocks";
import { beforeAll, beforeEach } from "vitest";

beforeAll(() => {
  initialize();
});

// Clear all mocks
beforeEach(() => {
  mockInstances.clearAll();
});

// Clear specific mocks
beforeEach(() => {
  mockInstances.clear(Map, Marker);
});

Extending mocks

You can add new mocks or extend the default mock instances to match your needs.

import { initialize, mocks, Map } from "google-maps-vitest-mocks";

beforeEach(() => {
  const MyCustomMapMock = vi.fn(() => ({
    getZoom: vi.fn(() => 10),
  }));
  initialize({ ...mocks, Circle: MyCustomMapMock });
});

Contributing

If you want to contribute to this repository and don't know how, please watch this tutorial. Here's a list of steps to follow:

  1. Fork the repository and create your branch.
  2. Run npm install in the repository root.
  3. If you've fixed a bug or added code that should be tested, please add tests.
  4. Ensure the test suite passes with npm run test.
  5. Make sure your code lints and follows this project code's style.
  6. Send a pull request specifying the type of commit:
    • feat: A new feature you're adding.
    • fix: A bug fix.
    • refactor: Refactoring a specific section of the codebase.
    • test: Everything related to testing.
    • docs: Everything related to documentation.
    • chore: Regular code maintenance.

License

Apache 2.0