instrumentation-client.js and Intercepting Routes in Next.js — Early Monitoring and Smart Navigation

The instrumentation-client.js file in Next.js lets you run monitoring, analytics, and polyfills before your app becomes interactive. Combined with Intercepting Routes, you can display content like modals without changing the page context. This article explains how to use both features with practical examples.

instrumentation-client.jsperformance monitoringIntercepting Routesmodal navigation

~2 min read · Updated Oct 29, 2025

1. instrumentation-client.js — Monitoring Before Interaction


This file runs at a specific point in the app lifecycle:

  • After the HTML document loads
  • Before React hydration
  • Before user interaction begins

Example:

// instrumentation-client.ts
performance.mark('app-init')
console.log('Analytics initialized')

window.addEventListener('error', (event) => {
  reportError(event.error)
})

Tracking Navigation:

export function onRouterTransitionStart(url, navigationType) {
  console.log(`Navigation started: ${navigationType} to ${url}`)
  performance.mark(`nav-start-${Date.now()}`)
}

Performance Monitoring:

const observer = new PerformanceObserver((list) => {
  for (const entry of list.getEntries()) {
    if (entry instanceof PerformanceNavigationTiming) {
      console.log('Time to Interactive:', entry.loadEventEnd - startTime)
    }
  }
})

observer.observe({ entryTypes: ['navigation'] })

Loading Polyfills:

import './lib/polyfills'

if (!window.ResizeObserver) {
  import('./lib/polyfills/resize-observer').then((mod) => {
    window.ResizeObserver = mod.default
  })
}

2. Intercepting Routes — Displaying Content Without Changing Context


Intercepting Routes let you load content from another route inside the current layout — perfect for modals and overlays.

Example:

Display a photo modal from /photo/123 inside the /feed page without changing the main view.


Matching Rules:

  • (.): same level
  • (..): one level up
  • (..)(..): two levels up
  • (...): from root app directory

Folder Structure:

To intercept the photo route inside feed, create a folder named (..)photo.


3. Practical Use Cases for Intercepting Routes


  • Photo modal in a gallery
  • Login modal in a navbar
  • Shopping cart in a side drawer

Benefits:

  • Shareable URLs for modal content
  • Preserve context on refresh
  • Close modal with back navigation
  • Reopen modal with forward navigation

Conclusion


The instrumentation-client.js file lets you set up monitoring and analytics before your app becomes interactive. Intercepting Routes enable dynamic overlays like modals without disrupting the user’s context. Together, they make your Next.js app smarter, faster, and more user-friendly.


Written & researched by Dr. Shahin Siami

Related Articles

Advanced Client-Side Routing and Performance Hooks in Next.js

Next.js provides a rich set of client-side hooks and caching utilities that empower developers to build dynamic, responsive, and secure applications. From reading route parameters to tracking navigation state and reporting performance metrics, this guide walks you through the most important tools available in the App Router.

Continue

Handling Authorization and Caching in Next.js: A Developer’s Guide

Next.js introduces powerful experimental features for access control and smart caching. This guide covers the unauthorized() function for custom 401 handling, unstable_cache for persistent memoization, updateTag for instant cache invalidation, and useLinkStatus for inline navigation feedback. Learn how to use these tools to build secure, performant, and responsive applications.

Continue

redirect and refresh in Next.js — Smart Redirects and Client Refreshing via Server Actions

The redirect function in Next.js allows you to navigate users to a new route, returning either a 307 or 303 HTTP response depending on context. It works in Server Components, Client Components, Route Handlers, and Server Actions. The refresh function is used exclusively within Server Actions to refresh the client router. This article explains how both functions work, with practical examples and key considerations.

Continue

NextRequest and NextResponse in Next.js — Managing Cookies, Headers, Redirects, and Rewrites

Next.js extends the native Web Request and Response APIs with NextRequest and NextResponse, offering powerful tools for managing cookies, headers, redirects, rewrites, and JSON responses. These utilities simplify server-side logic and improve control over routing, personalization, and security. This guide walks through their capabilities with practical examples and best practices.

Continue

headers, ImageResponse, notFound, and permanentRedirect in Next.js — Request Handling, Dynamic Images, Errors, and Redirects

Next.js offers powerful tools for handling HTTP requests and responses in Server Components. The headers function lets you read incoming request headers. ImageResponse allows you to generate dynamic images using JSX and CSS. The notFound function renders a custom 404 page, and permanentRedirect enables permanent redirection to another route. This article explains how to use each feature with practical examples.

Continue

A Complete Guide to Using metadata and generateMetadata in Next.js

In modern versions of Next.js, managing page metadata is more powerful and intuitive than ever. Metadata is automatically injected into the <head> of your pages and plays a vital role in SEO, social sharing, and user experience. This guide explains the two main ways to define metadata: using the static metadata object and the dynamic generateMetadata function.

Continue