-
Notifications
You must be signed in to change notification settings - Fork 25
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
Add Typescript Support #13
Comments
For this, we should probably use swc to transpile the TypeScript to JavaScript. |
And the next logical step would be to provide ts definitions of spiderfire functions. |
All modules already have TypeScript (and Flow) definitions created, I think it's mostly a matter of integrating those into IDEs and stuff. |
Yes, I totally forgot it. |
I can make a PR for this with some guidance, if you would like. |
Maybe swc-project/swc for bundling TS compiler within? |
That's the plan for the future, it's just that I don't want to deal with caching, which is going to be almost certainly required. |
I completely forgot about mentioning this here, but until full support is added, I've moved all TypeScript (and Flow) bindings to a seperate folder (00c02d4). This will be published as a zip file in each prerelease. Bindings: https://github.com/Redfire75369/spiderfire/tree/master/bindings |
As of 9e05f8c, typescript support has been added! You'll still need the global declaration files for your IDE but this is a good step forward. There's also no support for something like |
I know, I know this is a deno thing but I really think it would improve the project by attracting all the typescript folks.
Personally is something node.js needs and I'd use it without doubt. I'm not suggesting get rid of javascript, not at all, what I'm suggesting is let the users use typescript or javascript without too much configuration or boilerplate.
I'm still learning rust but I'd like to work/collaborate on this feature.
The text was updated successfully, but these errors were encountered: