# TypeScript issue with PrismicNextLink

**URL:** <https://community.prismic.io/t/typescript-issue-with-prismicnextlink/17781>\
**Category:** Developing with Prismic\
**Tags:** nextjs, typescript\
**Created:** [October 7, 2024, 5:38pm UTC](https://community.prismic.io/t/typescript-issue-with-prismicnextlink/17781 "2024-10-07T17:38:53Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Ezekiel](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@Ezekiel](https://community.prismic.io/u/Ezekiel)\
**Post date:** [November 7, 2024, 8:53am UTC](https://community.prismic.io/t/typescript-issue-with-prismicnextlink/17781/8 "2024-11-07T08:53:56Z")

</div>

For anyone else running into this issue, Josh found the solution in the following thread:

> [@PrismicNextLink throwing error when trying to deploy](https://community.prismic.io/t/prismicnextlink-throwing-error-when-trying-to-deploy/17902/12):
>
> I got it working! Went back in and ran through the prismic setup again and I guess I picked up some new packages

It was related to package dependencies. To guarantee up-to-date packages, you can run `npx npm-upgrade@latest`, delete the `node_modules` folder, and re-install all the dependencies.

---

_[View the full topic](https://community.prismic.io/t/typescript-issue-with-prismicnextlink/17781)._
