-
-
Notifications
You must be signed in to change notification settings - Fork 622
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
feat(cli): TypeScript support #550
Conversation
* docs(pkg): readme info Created read me file for info sub package * docs(readme): added usage example * Updated usage * Fixed correct package * docs(info): small typo
* docs(pkg): readme info Created read me file for info sub package * docs(readme): added usage example * Updated usage * Fixed correct package * docs(info): small typo
* docs(pkg): readme file for add package * docs(add): fix missing content
There are issues when we import TS compiled JS files into JS because TS compiles default exports to `default` named import/export which makes it not possible to import inside JS directly. Some of the ways to fix this is using .default in all calls or avoid using default export/import totally. Ref: https://basarat.gitbooks.io/typescript/docs/tips/defaultIsBad.html
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
Are we ready? 😃 Please update the template. It's an important PR, let's give nice visibility |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to finish the bin folder first and then we can publish a breaking change. No need to rush this :)
What kind of change does this PR introduce?
Did you add tests for your changes?
If relevant, did you update the documentation?
Summary
Does this PR introduce a breaking change?
Other information
Closes #245