Use isolatedModules for easier compatibility with Deno (and others) #827
+34
−22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the driver's TypeScript code to use TypeScript's stricter
isolatedModules
flag.isolatedModules
is required to support some transpilers that operate on a single file at a time, so they can tell which imports/exports contain only type information and are safe to discard. This change is more "strict" and does not change the API, so is completely backwards compatible.Rationale: The reason for this PR is to allow a common codebase to work for both Node.js and Deno. While TypeScript/Node don't care if isolatedModules is enabled or not, Deno requires it. So this is a prerequisite to supporting Deno. See the relevant forum discussion. I will soon be opening a PR that shows how to generate a Deno driver, which depends on this change.
Without this change, Deno will report this TypeScript error when trying to transpile the driver code: