Closed andrewiggins closed 1 year ago
Latest commit: f8357cb4ebc69b438e507c6bedc5b42428a9f221
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 | f8357cb4ebc69b438e507c6bedc5b42428a9f221 |
Latest deploy log | https://app.netlify.com/sites/preact-signals-demo/deploys/64a6e2b01737ea0008ecdbae |
Deploy Preview | https://deploy-preview-377--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.
Size Change: -7 B (0%)
Total Size: 69.3 kB
Filename | Size | Change |
---|---|---|
docs/dist/assets/client.********.js |
46.6 kB | +2 B (0%) |
docs/dist/nesting-********.js |
1.13 kB | -1 B (0%) |
docs/dist/react-********.js |
238 B | -1 B (0%) |
packages/react/dist/signals.js |
1.25 kB | -3 B (0%) |
packages/react/dist/signals.mjs |
1.2 kB | -4 B (0%) |
I forgot to include the mangle.json pointer in the new package.json so some property names weren't being properly mangled.
Note: no tests fail because currently
@preact/signals-react
bundles the runtime package inside of it's bundled output and those properties are mangled - it doesn't import from/runtime
. I left that as is for now since the/runtime
package is intended to be an internal detail that will likely change in the future. I discovered this while working on the babel transform which does import from/runtime
directly.