-
Notifications
You must be signed in to change notification settings - Fork 55
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
Migrate code base to typescript #686
Comments
I think the ts-node should allow transpilation of typescript along with ES6 code to browser compliant es5 code. Maybe it internally uses a build tool ( like babel ). We might not have to explicitly specify the tool (#687). tsc wiill take care of build ( might have to provide config file in cases of advanced build) |
@sacOO7 That makes sense to me. I don't think I've ever used Typescript as a transpiler (I'm used to working in React projects where Babel is necessary to transform JSX anyway) but if we can get by without depending on Babel at all then I'm all for it 👍 |
Yes, we might not have to rely on babel. Personally, I would always go with +1 for typescript. It works like charm in single-threaded env. like browser 🥇 |
➤ Owen Pearson commented: Issue split into: SDK-694Set up initial typescript toolchain |
please don't migrate to typescript. It's possible to have strict type checking without the need of typescript syntax and extra compile overhead if you just use JSDoc. Beside ESM and typescript don't work well together right now... |
Using typescript with strict type-checking will allow us to enforce better type safety in the project and will allow us to emit type definition files as part of the compile process rather than having to maintain them ourselves.
┆Issue is synchronized with this Jira Story by Unito
The text was updated successfully, but these errors were encountered: