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

build: use babel cli's --extensions consistently in all packages #1575

Merged
merged 1 commit into from
May 3, 2019

Conversation

michaelsbradleyjr
Copy link
Contributor

If a package uses only .js then supply --extensions ".js". If a package uses only .ts then supply --extensions ".ts". If a package uses both, then supply --extensions ".js,.ts".

The reason for this is that adding/removing TS/JS support ought to occasion revising a package's package.json file and adjusting other scripts as well, e.g. for linting. With these changes, it won't work to simply start adding .ts files in a package's src/ directory, which should prompt the developer to review package.json and make the appropriate changes, and/or other developers may realize changes need to be made during code review.

If a package uses only `.js` then supply `--extensions ".js"`. If a package
uses only `.ts` then supply `--extensions ".ts"`. If a package uses both, then
supply `--extensions ".js,.ts"`.

The reason for this is that adding/removing TS/JS support ought to occasion
revising a package's `package.json` file and adjusting other scripts as well,
e.g. for linting. With these changes, it won't work to simply start adding
`.ts` files in a package's `src/` directory, which should prompt the developer
to review `package.json` and make the appropriate changes, and/or other
developers may realize changes need to be made during code review.
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