Build @fluent/dom with TypeScript #474
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See #376 for the larger discussion about migrating
@fluentpackages to TypeScript. See #470 for the discussion about the status of@fluent/dom.This PR is different than the others related to the TypeScript migration. As I explained in #470, I think fully migrating
@fluent/domto TypeScript would add little value to it today. However, I'd like to move forward with my build system cleanups; this PR switches@fluent/dom's build system to usingtscto transpile JS files to JS files with inferred type definitions. This way, all@fluentpackages are built using the same set of tools.