Closed dcporter closed 10 months ago
Latest commit: 990f1eb36fa4ab5e30029f79ceeccf709137d14d
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
Name | Link |
---|---|
Latest commit | 990f1eb36fa4ab5e30029f79ceeccf709137d14d |
Latest deploy log | https://app.netlify.com/sites/preact-signals-demo/deploys/6564ae8a9f46d80008d5f8c2 |
Deploy Preview | https://deploy-preview-451--preact-signals-demo.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
The change was originally made by @eddyw in #231 (a very cool PR otherwise) — wanted to @ Eddy in to make sure I'm not missing any big consequences here.
What is a problem to upgrade typescript?
This syntax (export { type Foo }) insta-breaks the build for any project using versions of TS earlier than v4.5. Verified locally that this change fixes the build for earlier versions while not breaking it for later versions.
I believe the only scenario in which this change could impact tree-shaking is if someone is only importing the
ReadonlySignal
type in a project that doesn't otherwise use signals, which seems unlikely.