Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(compartment-mapper): there's more benefit to keeping __esModule flag than not #1145

Merged
merged 3 commits into from Apr 11, 2022

Conversation

naugtur
Copy link
Member

@naugtur naugtur commented Apr 6, 2022

compiled TS depends on it across packages.

var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};

https://www.typescriptlang.org/tsconfig#esModuleInterop

…lag than not (compiled TS depends on it across packages)
@kriskowal
Copy link
Member

Can you frame this requirement as a test?

@naugtur
Copy link
Member Author

naugtur commented Apr 7, 2022

Can you frame this requirement as a test?

I did, but in e2e tests. Will do.

@naugtur naugtur merged commit c769447 into master Apr 11, 2022
@naugtur naugtur deleted the naugtur-esmodule-stays branch April 11, 2022 09:14
naugtur added a commit that referenced this pull request May 16, 2022
…lag than not (#1145)

* fix(compartment-mapper): there's more benefit to keeping __esModule flag than not (compiled TS depends on it across packages)

* test(compartment-mapper): cover the presence of __esModule flag for typescript esModuleInterop compatibility
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.

None yet

2 participants