Skip to content

Remove semicolon after TypeScript interface definition#15827

Merged
dhruvmanila merged 1 commit intoastral-sh:mainfrom
leotaku:remove-semicolon
Jan 30, 2025
Merged

Remove semicolon after TypeScript interface definition#15827
dhruvmanila merged 1 commit intoastral-sh:mainfrom
leotaku:remove-semicolon

Conversation

@leotaku
Copy link
Copy Markdown
Contributor

@leotaku leotaku commented Jan 30, 2025

Summary

This PR removes a trailing semicolon after an interface definition in the custom TypeScript section of ruff_wasm. Currently, this semicolon triggers the error "TS1036: Statements are not allowed in ambient contexts" when including the file and compiling with e.g tsc.

Test Plan

I made the change, ran wasm-pack and copied the generated directory manually to my node_modules folder. I then compiled a file importing @astral-sh/ruff-wasm-web again and confirmed that the compilation error was gone.

This removes a trailing semicolon after an interface definition in
the custom TypeScript section.  Currently, this semicolon triggers
the error "TS1036: Statements are not allowed in ambient contexts".
@leotaku leotaku changed the title [ruff_wasm] Remove semicolon after TypeScript interface definition Remove semicolon after TypeScript interface definition Jan 30, 2025
@github-actions
Copy link
Copy Markdown
Contributor

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

leotaku added a commit to leotaku/jupyter-ruff that referenced this pull request Jan 30, 2025
@dhruvmanila dhruvmanila added internal An internal refactor or improvement bug Something isn't working and removed internal An internal refactor or improvement labels Jan 30, 2025
@dhruvmanila dhruvmanila merged commit b0b8b06 into astral-sh:main Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants