[Request]: Using Generated types in your frontend application

[atissedrescaleway]

Summary

The documentation for using generated Strapi types is outdated and unofficial .

Why is it needed?

It's unclear at the moment how to clearly use generated types in your frontend with Strapi V5.

Suggested solution(s)

No response

Related issue(s)/PR(s)

No response

[github-actions]

👋 Thank you for your contribution!

❄️ We are currently in an end-of-year contribution freeze period.
For more information, please check our announcement.

Your issue will be processed once contributions resume.

Thank you for your understanding!

[github-actions]

🤖 I've analyzed your question and here's what I found:

Hi there! Thank you so much for raising this important point and for being proactive in helping improve the Strapi developer experience. We truly appreciate your engagement and the time you took to highlight the need for clearer guidance on using generated Strapi types in frontend applications.

You're absolutely right: as of now, the official Strapi documentation does not provide a dedicated, up-to-date guide for directly using the generated backend types in frontend projects. The only reference currently available is an unofficial workaround mentioned in the docs, which points to the strapi-typed-frontend community project. This is not an official solution, and we understand how this can be confusing or limiting for developers working with Strapi v5 and TypeScript frontends.

Current State & Workarounds

• Official Support: At this time, Strapi does not officially support exporting or consuming backend-generated types directly in frontend applications. The types generated by the strapi ts:generate-types command are intended for backend use and are not designed for direct frontend consumption. This is noted in the TypeScript development documentation, which suggests the community workaround but does not provide an official method.
• Workaround: If you wish to experiment, you can manually copy the generated types from the backend's types directory into your frontend project. However, please be aware that these types may change with Strapi updates, and this approach is not officially supported or guaranteed to be stable. The documentation also cautions that types should only be imported from @strapi/strapi for backend use, as internal types may change without notice.

What You Can Do

1. Manual Copy (Unofficial):
   • Run strapi ts:generate-types in your backend project.
   • Copy the relevant type definitions from the backend's types directory to your frontend project.
   • Remove any backend-specific declarations (like declare module '@strapi/types') to avoid conflicts.
   • Use these types in your frontend code as needed.
2. Stay Updated: Keep an eye on the official TypeScript documentation for any updates or new features regarding type sharing between backend and frontend.
3. Community Resources: For more ideas or to discuss best practices, you can join the Strapi Discord or post in the Strapi Forum. The community is very active and may have additional tips or evolving solutions.

Next Steps

• If you believe official support for frontend type sharing would be valuable, we encourage you to submit a feature request or upvote existing ones at feedback.strapi.io. This helps the core team prioritize features that matter most to the community.
• If you encounter any issues or bugs with the current type generation process, please let us know, or if you think this is a core product issue, we can flag it for the core team (@pwizla).

Thank you again for your feedback and for helping make Strapi better for everyone! If you have further questions or want to share your use case, please feel free to continue the conversation here or in our community channels.

Warm regards,
The Strapi Team

References:

• TypeScript Development with Strapi
• TypeScript in Strapi

📚 Relevant documentation:

• Adding TypeScript support to existing Strapi projects
• Command Line Interface (CLI) - strapi ts:generate-types
• Community & Support
• Database migrations - Handling migrations with TypeScript code
• Documentation plugin - registerOverride()
• Entity Service API to Document Service API migration reference - Manual migration
• Frequently Asked Questions - Can I use TypeScript in a Strapi project?
• GraphQL plugin - Shadow CRUD
• Manipulating documents and entries
• Project structure
• Release notes - 5.2.0
• TypeScript
• TypeScript configuration
• TypeScript Development with Strapi

---

ℹ️ This response was generated automatically. If this doesn't fully answer your question or if you need further assistance, please mention @pwizla in a comment and a human maintainer will help you.

You can also try our interactive AI chat for more detailed assistance.

💡 For feature requests or product feedback, visit feedback.strapi.io.

[atissedrescaleway]

Closing this since the Strapi SDK appears to be the chosen direction