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

maps-backend-challenge

v1.0.7

Published

A developer on our team was working on integrating the TomTom API. They did a great job laying the groundwork, but they've recently been promoted to a new project that requires their full attention.

Downloads

13

Readme

Scenario:

A developer on our team was working on integrating the TomTom API. They did a great job laying the groundwork, but they've recently been promoted to a new project that requires their full attention.

We are pretty confident the developer managed to complete the majority of the initial part of the integration, however there might be a bug or two to be discovered.

Your task is to finish off this implementation, ensuring the requirements are met with passing tests.

Task:

To take a partial address input and return full address suggestions along with the address broken into its individual components using the TomTom API.

Resources:

Place Search Documentation: https://developer.tomtom.com/search-api/documentation/search-service/search-service API Key:

Install:

  1. yarn install

Test:

  1. yarn install
  2. yarn test

Requirements:

  1. All tests should pass and ensure good coverage for new work
  2. We only allow Australian addresses to be returned
  3. Code should be maintainable and consistent
  4. The result elements should contain important information about the place (country, municipality, etc)
  5. The returned result should be typed and easily consumable via users of the library
  6. No front-end requirements are necessary, this is purely a backend NodeJS library

Notes from candidate (Rahul Samaranayake) for reviewers

  • I noticed a bug in getPlaceAutocomplete(), where it was sending only a destructured object value for placeId.
  • I've added additional tests to cover the payload content. However, since this TomTom endpoint seems non-deterministic, I'm unsure how stable the tests will be.
  • I've added interfaces to make the code type-safe.
  • getAutoCompleteDetails() has been updated so the client can pass the country code.
  • You can install this package to a project with yarn add maps-backend-challenge -> https://www.npmjs.com/package/maps-backend-challenge