ionic-team / ionic-team/ionic-framework
bug: Component types missing when consumed from Stencil
- Ngôn ngữ chính
- TypeScript
- Star
- 52.7k
- Fork
- 13.3k
- Merge trung bình
- 1 ngày 15 giờ
- Pull request đã merge (30 ngày)
- 51
Mô tả
### Prerequisites
- [x] I have read the [Contributing Guidelines](https://github.com/ionic-team/ionic-framework/blob/main/docs/CONTRIBUTING.md#creating-an-issue).
- [x] I agree to follow the [Code of Conduct](https://ionicframework.com/code-of-conduct).
- [x] I have searched for [existing issues](https://github.com/ionic-team/ionic-framework/issues) that already report this problem, without success.
### Ionic Framework Version
v8.x
### Current Behavior
I have a Stencil project where I consume `@ionic/core`. Starting with 8.2.9, the types for `ion-*` elements in the TSX files are no longer available. If I downgrade to 8.2.8, all is good.
When hovering in VS Code:
* 8.2.8: `(property) LocalJSX.IntrinsicElements["ion-item"]: LocalJSX.IonItem & JSXBase.HTMLAttributes`
* 8.2.9: `(index) IntrinsicElements[string]: any`
And the project won't compile because of `Parameter 'ev' implicitly has an 'any' type.` on all event handlers.
### Expected Behavior
Types should be available.
### Steps to Reproduce
1. `npm init stencil`
2. Select `ionic-pwa [community]`
3. cd into project, `npm install`
4. *Inspect elements in VS Code.* (`IntrinsicElements[string]: any`)
5. `npm i @ionic/core@8.2.8`
6. *Inspect elements in VS Code.* (`LocalJSX.IntrinsicElements["ion-..."]:`)
7. `npm i @ionic/core@8.2.9`
8. *Inspect elements in VS Code.* (`IntrinsicElements[string]: any`)
### Code Reproduction URL
-
### Ionic Info
npm 10.9.2
node 23.11.0
@ionic/core 8.2.9
@stencil/core 4.36.3
### Additional Information
_No response_
Hướng dẫn đóng góp
Hướng nghiên cứu
Reproduce the issue with the documented Stencil project steps using @ionic/core 8.2.8 and 8.2.9, then inspect the generated TSX types in VS Code. Done means ion-* intrinsic element types are available again and event handlers no longer produce implicit-any errors.
Do mô hình lập chỉ mục viết ra từ nội dung của issue.
Đánh giá
- Công nghệ
- typescript
- Lĩnh vực
- frontend
- Loại issue
- Lỗi
- Độ khó
- 3/5
- Thời gian dự kiến
- 1-2 ngày
- Mức độ hoạt động
- Đình trệ
- Độ rõ ràng
- Khá rõ ràng
- Mức phù hợp với người mới
- 48/100