[React 19] Publishing the TypeScript declaration of `babel-plugin-react-compiler`

[SukkaW]

Description

I am currently integrating React's new experimental compiler into my projects, specifically through the development of a Next.js plugin and a webpack loader, which can be found here: react-compiler-webpack. During this process, I've encountered an issue where the TypeScript definitions for the new compiler are not available on npm. Since the compiler itself is written in TypeScript, having these definitions available would be immensely beneficial for ensuring type safety and enhancing developer productivity, especially in complex projects like Next.js and webpack plugins.

Expected Behavior

The TypeScript definitions for React's new experimental compiler should be published to npm, allowing developers to import and use these definitions seamlessly in TypeScript-based projects.

Current Behavior

The TypeScript definitions are not currently available on npm, which complicates the development process for TypeScript users who need to ensure type safety and utilize IDE features like auto-completion and inline documentation.

Proposed Solution

I kindly request that the TypeScript definitions for the new experimental compiler be published to npm. This would not only aid in my current project but also benefit the broader TypeScript and React communities who are experimenting with or adopting the new compiler.

Thank you for considering this request. I am looking forward to any updates and am happy to assist in the testing or development of these definitions if needed.

[poteto]

We didn't include types in the npm package because the babel plugin doesn't have an external API that we want to expose. The only way we recommend to consume it is inside of a Babel compatible pipeline as a plugin. Is your use case mainly to type the config that the compiler accepts?

[SukkaW]

type the config that the compiler accepts

Yeah. That would be the only usage case.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[SukkaW]

Un-stale.

[SukkaW]

@poteto Just a friendly ping: please disable noEmit in rollup.config.js here: https://github.com/facebook/react/blob/main/compiler/packages/babel-plugin-react-compiler/rollup.config.js

babel-plugin-react-compiler is already written in TypeScript, it doesn't make sense to not generate TypeScript definitions as well.

[josephsavona]

We are intentionally not publishing typescript types directly from the compiler because the internal API and options are all experimental. We strongly recommend against using any internal APIs. For the config options, there are just a handful we expect to include in the stable release, and we can provide custom typescript declarations for these.

[SukkaW]

We are intentionally not publishing typescript types directly from the compiler because the internal API and options are all experimental. We strongly recommend against using any internal APIs. For the config options, there are just a handful we expect to include in the stable release, and we can provide custom typescript declarations for these.

The use case remains the same: building integration based on the react compiler. React doesn't have any official bundler plugin and it's up to the community to build that. At least the option type should be exported.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!