---
title: "Comment by Ignacio Lopezosa Serrano on \"Introducing Massimo\" | Hashnode"
description: "Just to be completely sure. I guess it’s compatible with Next.js (server side and browser side) with the native fetch approach. Is it? Is there any catch?"
url: "https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8/comment/68b6f71e247042aa63186ea4"
---

[Discussion](https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8)

Comment [Introducing Massimo](https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8)

[Ignacio Lopezosa Serrano](https://hashnode.com/@nacholopezosa)

[Sep 2, 2025](https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8/comment/68b6f71e247042aa63186ea4)

Just to be completely sure. I guess it’s compatible with Next.js (server side and browser side) with the native fetch approach. Is it? Is there any catch?

[Matteo Collina](https://hashnode.com/@matteocollina)

Open Sourcerer, Node.js TSC member, Fastify Lead Maintainer

[Sep 2, 2025](https://hashnode.com/posts/introducing-massimo/68b5a6e7c64a42983ebe6fc8/comment/68b6f71e247042aa63186ea4#reply-68b702689e96f4ce75e7bbdc)

Yes, the native fetch approach is compatible 100% with Next.js. No catch, no dependencies.