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

TypeScript support #18780

Closed
epixa opened this issue May 3, 2018 · 1 comment
Closed

TypeScript support #18780

epixa opened this issue May 3, 2018 · 1 comment
Assignees
Labels
build dev enhancement New value added to drive a business result Team:Operations Team label for Operations Team

Comments

@epixa
Copy link
Contributor

epixa commented May 3, 2018

Before we can start using TypeScript, we need proper support for TypeScript in our build system. The compilation process should be handled through the same process that handles our ECMAScript compilation, so people can develop using both TypeScript and ECMAScript simultaneously without juggling build tasks.

We should not ship TypeScript with builds of Kibana, so we can't simply add this to the existing optimizer. Effectively, this means we must first remove the optimizer.

edit: We are going to add support for TypeScript to the optimizer during development and will transpile code from TS to JS while building the distributable (and plugin distributables), just like we transpile all JS with babel to lighten the load of babel-register and the optimizer in production.

Blocked by #7322

@epixa epixa added dev Team:Operations Team label for Operations Team build enhancement New value added to drive a business result labels May 3, 2018
@epixa
Copy link
Contributor Author

epixa commented May 3, 2018

@elastic/kibana-operations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build dev enhancement New value added to drive a business result Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

2 participants