---
title: "Discussion on \"The Navigation API: Stop Wrestling with history.pushState\" | Hashnode"
description: "Discussion on \"The Navigation API: Stop Wrestling with history.pushState\". If you have ever hand-rolled a router, you know the ritual. You call history.pushState, then you wire up a popstate listener, then you discover popstate does not fire for pushState so you patch the UR"
url: "https://hashnode.com/posts/the-navigation-api-stop-wrestling-with-history-pushstate/6a437b0d960fb33e4a312c39"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Navigation API: Stop Wrestling with history.pushState](https://grimicorn.hashnode.dev/the-navigation-api-stop-wrestling-with-history-pushstate?utm_source=hashnode&utm_medium=feed)

If you have ever hand-rolled a router, you know the ritual. You call history.pushState, then you wire up a popstate listener, then you discover popstate does not fire for pushState so you patch the UR

Jun 30 · 4 min read · grimicorn.hashnode.dev  
Read the article

-   [#javascript](https://hashnode.com/tag/javascript)
-   [#routing](https://hashnode.com/tag/routing)
-   [#spa](https://hashnode.com/tag/spa)

## Written by

[Dan Holloran](https://hashnode.com/@grimicorn)

@grimicorn · St. Louis, MO

  
[View profile](https://hashnode.com/@grimicorn)

Full-stack web developer since 2012 · Vue · React · Laravel · danholloran.me

Senior Full Stack Developer with 14+ years building performant, scalable web applications. Passionate about architecture, mentorship, and finding the right tool for the job.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
