Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"error occured in dts build" without any other details #680

Closed
IanVS opened this issue Jul 27, 2022 · 1 comment · Fixed by #682
Closed

"error occured in dts build" without any other details #680

IanVS opened this issue Jul 27, 2022 · 1 comment · Fixed by #682

Comments

@IanVS
Copy link
Contributor

IanVS commented Jul 27, 2022

Hi, I am getting error occured in dts build, but there are no other details about the error, or why it is occurring. It happens when I change a type in one of my types.ts files from an express Router to a fastify FastifyInstance, but I have no idea why. I see where the error is being created in dtsTask, but is it possible to add some extra debugging information to help troubleshoot why I have a failure?

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
@IanVS
Copy link
Contributor Author

IanVS commented Jul 27, 2022

I was able to get some details about the error by tweaking tsup in node_modules

- logger.error("dts", "Build error");
+ logger.error("dts", error.message);

which gave me something I could dig into:

'FastifyError' is not exported by ../../node_modules/@fastify/error/index.d.ts, imported by ../../node_modules/fastify/types/hooks.d.ts

I guess that error is due to #14. I'm not sure how to solve it, but the main issue here is that the underlying error was not reported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant