Skip to content

Conversation

@wjhsf
Copy link
Contributor

@wjhsf wjhsf commented Dec 16, 2025

I enabled isolatedDeclarations and fixed everything that made sense. Fully enabling the flag requires creating explicit types for the error info objects in @lwc/errors, which would be tedious, so I skipped that and disabled the flag.

I enabled isolatedModules and fixed everything that made sense. We can't use const enum with isolated modules, but we like them because they minify cleanly, so I skipped that and disabled the flag.

I enabled erasableSyntaxOnly and fixed everything that made sense. We can't use const enum with isolated modules, but we like them because they minify cleanly, so I skipped that and disabled the flag. (I did replace our regular enum with objects.)

I enabled `isolatedDeclarations` and fixed everything that made sense.
Fully enabling the flag requires creating explicit types for the error info objects in `@lwc/errors`,
which would be tedious, so I skipped that and disabled the flag.

I enabled `isolatedModules` and fixed everything that made sense.
We can't use `const enum` with isolated modules, but we like them because they minify cleanly,
so I skipped that and disabled the flag.

I enabled `erasableSyntaxOnly` and fixed everything that made sense.
We can't use `const enum` with isolated modules, but we like them because they minify cleanly,
so I skipped that and disabled the flag.
(I did replace our regular `enum` with objects.)
@wjhsf wjhsf requested a review from a team as a code owner December 16, 2025 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants