feat(react): migrate to new React Output Target with Next.js support

[christian-bromann]

What is the current behavior?

We have done a lot of work to update the @stencil/react-output-target package to use the Lit wrapper as well as Next.js support. We are at a point where we would like to test the state of the new output target package with ecosystem projects to validate its functionality.

What is the new behavior?

The new output target provides:

• a bunch of bug fixes due to changes how we wrap Stencil components using the @lit/react wrapper package
• it exports a runtime now which requires @stencil/react-output-target to be a dependency
• support for using Ionic within Next.js applications

Does this introduce a breaking change?

• Yes
• No

So far I don't see a reason why this could break someones existing code base. That said, more testing is needed to verify this.

Other information

Unfortunately we can't use @stencil/react-output-target yet due to the fact that it requires a more modern moduleResolution like node16 or bundler. The current one (node) is meant to be used for for Node.js versions older than v10, which only support CommonJS require. I've create a separate issue for this.

Update: raised a PR #29717 to enable export maps

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ionic-framework	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 16, 2024 5:43pm