https://github.com/lumakernel/issue-dt-estree-jsx
https://github.com/lumakernel/issue-dt-estree-jsx
Last synced: about 13 hours ago
JSON representation
- Host: GitHub
- URL: https://github.com/lumakernel/issue-dt-estree-jsx
- Owner: LumaKernel
- License: cc0-1.0
- Created: 2024-02-12T09:44:01.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-02-12T10:32:54.000Z (over 2 years ago)
- Last Synced: 2025-10-13T09:26:19.315Z (8 months ago)
- Language: TypeScript
- Size: 16.6 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Issue Definitely Typed estree-jsx
NOTE: There're no correspoind runtime package.
PR: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/68598
First, see `main.ts` or output of that in `main.ts.out.txt`. (This is made by `bun run ./main.ts > ./main.ts.out.txt`)
You can see this part:
```js
// ...
data: {
estree: {
type: 'Program',
// ..
body: [
{
type: 'ExpressionStatement',
expression: {
type: 'JSXFragment',
// ...
```
This is result of parse of MDX `{<>hi>}`.
This shows type `JSXFragment` is allowed as top level expression of estree.
In JSX, Fragment expression (`<>...>`) is also an expression like as JSX normal expression (`...`).
Allowed `type` values are managed by interface extension, so we need to fix `@types/estree-jsx`.