---
title: "Comment by Grace Frank on \"Next.js 13 Route Handlers with Typescript\" | Hashnode"
description: "Also if I install a dependency, how will next.js know that the dependency is just for the frontend and not the backend?"
url: "https://hashnode.com/posts/nextjs-13-route-handlers-with-typescript/648f2b23a3d4a7216732ba47/comment/64a28ea78db091c401036f70"
---

[Discussion](https://hashnode.com/posts/nextjs-13-route-handlers-with-typescript/648f2b23a3d4a7216732ba47)

Comment [Next.js 13 Route Handlers with Typescript](https://hashnode.com/posts/nextjs-13-route-handlers-with-typescript/648f2b23a3d4a7216732ba47)

[Grace Frank](https://hashnode.com/@gracey)

[Jul 3, 2023](https://hashnode.com/posts/nextjs-13-route-handlers-with-typescript/648f2b23a3d4a7216732ba47/comment/64a28ea78db091c401036f70)

Also if I install a dependency, how will next.js know that the dependency is just for the frontend and not the backend?

[Mary Etokwudo](https://hashnode.com/@uniqcoda)

[Jul 3, 2023](https://hashnode.com/posts/nextjs-13-route-handlers-with-typescript/648f2b23a3d4a7216732ba47/comment/64a28ea78db091c401036f70#reply-64a3275f0d9d87e57bd724c8)

I think that by default, Next.js will try to make all the dependencies available on the frontend except those that need to run on a node environment. Check this [Q&A on server-side dependencies](https://trueq.io/q/2) as well.
