Closed remcohaszing closed 3 months ago
Name | Link |
---|---|
Latest commit | d5888e656b59b042ddca31e6e4fbcf35d4da5f18 |
Latest deploy log | https://app.netlify.com/sites/shiki-matsu/deploys/666ad33f92bcff0008e68962 |
Deploy Preview | https://deploy-preview-699--shiki-matsu.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.
Name | Link |
---|---|
Latest commit | d5888e656b59b042ddca31e6e4fbcf35d4da5f18 |
Latest deploy log | https://app.netlify.com/sites/shiki-next/deploys/666ad33f389a88000894b391 |
Deploy Preview | https://deploy-preview-699--shiki-next.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.
Description
The augmented hast
Data
interface conflicts withElementData
frommdast-util-to-hast
. The augmentation is redundant, so itβs removed entirely.The augmented hast
Properties
interface was redundant and invalid. Instead, the value is now converted to string in the place it is used.Linked Issues
https://github.com/DefinitelyTyped/DefinitelyTyped/discussions/69775
Additional context
You should only augment interfaces if you define something, not if you consume it.