Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
@Dunqing One failing test |
✅ Deploy Preview for rolldown-rs canceled.
|
Benchmarks Rust |
// declare-class.ts
declare class foo {}
export default foo
export let bar = 123The above code will transform into: export let bar = 123;See OXC Playground. Our implementation exactly match with But in ESBuild, the I am not sure which way we should follow, and okay to follow your guy's suggestion to change? What do you think? Also, take into account that @rolldown/rolldown cc |
|
Then the only way to workaround this issue is omit |
This comment was marked as outdated.
This comment was marked as outdated.
…portee module is ts/tsx (#4147) <!-- Thank you for contributing! --> ### Description 1. related to #4144 (comment) <!-- Please insert your description here and provide especially info about the "what" this PR is solving -->
49acc2f to
ad340ec
Compare
|
I found that the changes at 3c473d0 were unexpected due to oxc-project/oxc#10465. But this only affects DTS, and has no type resolution change, whether it has |
Pull Request is not mergeable
) There are multiple cases that `MISSING_EXPORT` happens even when TypeScript does not output an error. 1. #4144 (comment) - This case only happens when the importer and the importee is both TS. This is because we treat `foo` as a "type" rather than a "value" (since we remove `export default foo` completely. If we treat it as a "value", we should keep that). 2. The case written in https://www.typescriptlang.org/tsconfig/#verbatimModuleSyntax (`export { A } from './a'`) - This case only happens when the importer and the importee is both TS. This is because if `A` is a "value", `A` would exist after transpilation. Both of these cases can be fixed by adding the `type` modifier. While setting `verbatimModuleSyntax: true` would make TypeScript to error on these cases, it changes some other behaviors, and is not straightforward to turn that on. This PR improves the error message, so that users can know what to do even if they don't enable `verbatimModuleSyntax`. refs #4147
No description provided.