pyxle-langkit 0.3.5

What's new

• Unclosed JSX tags are reported at the open tag — and always named. Babel anchors an unclosed-tag error where it detects the problem: some later closing tag (lines below the real mistake), or a tag-less "Unterminated JSX contents" when the unclosed element is outermost. The extractor now locates the innermost unclosed open tag itself and reports <section> is never closed — add the matching </section> or make the tag self-closing. anchored at that tag's line, with a machine-readable code: "unclosed_jsx_tag". Mismatched-closing-tag messages are unchanged.
• pyxle-langkit lint's React analysis works on a clean install. The React parser runner now ships as a self-contained bundle (Babel inlined), so linting no longer depends on @babel/parser being installed next to the toolkit. A genuinely unavailable analyzer (Node missing, timeout) now surfaces as a single error-severity react/analyzer-unavailable diagnostic that fails the lint, instead of exiting 0 with misleading rule warnings.

Full details in the changelog.

v0.3.4 — extractor: duplicate-export detection + clearer JSX errors

Powers the sharper pyxle check in pyxle-framework 0.6.1.

• Detects duplicate export default (Babel accepts it, esbuild rejects it at build).
• Strips Babel's snippet-relative (line:col) from messages and hints on unclosed { } ("Unterminated regular expression").
• Also ships the previously-unreleased TypeScript-in-client-block guard.

v0.3.3

What's changed

• pyxle check works on a clean install. The JSX checker's Babel parser dependencies (@babel/parser, @babel/traverse) are now bundled into a self-contained extractor shipped in the wheel, so pyxle check runs after pip install 'pyxle-framework[langkit]' with zero extra npm setup. A missing-dependency failure now names the exact packages instead of an opaque error.
• Fixed stale GitHub org URLs (pyxle-framework → pyxle-dev) in the package metadata and the VS Code extension manifest.

Pairs with pyxle-framework 0.4.2.