Open jadonk opened 6 years ago
From @troywweber7 on August 15, 2017 16:27
I'm also not an expert at writing typescript definitions, so I may have gone about it wrong. Open to criticism.
@troywweber7 this is pretty cool. Sorry I'm just now getting around to checking it out. I've got some urgent bugs/features to add for Blue/PocketBeagle support, but will try to get this in for my next major release.
From @troywweber7 on December 29, 2017 21:57
@jadonk eventually I intend to submit this to DefinitelyTyped repository so anyone can npm i -D @types/bonescript
. However, as I should probably confirm all the shapes before I do. And when someone does submit it to DT, they would likely ping you on their repo for input anyway.
Ultimately, definitely typed recommends bundling the type definition file in your project if possible. To do that, one would just add an entry to package.json
for { "types" : "path/to/index.d.ts" }
. But that is of course up to the project maintainer, and a lot of JS library maintainers opt not to bundle because they don't want the responsibility of updating the definition file when they update the api.
Anyway, as a final thought (for now), I'm using it in multiple projects, so I have cheated for now and am temporarily hosting here and it can be installed in a project with npm i -D bitbucket:webercode/types-bonescript
.
Cheers.
From @troywweber7 on August 9, 2017 0:10
I might submit this as a pull request at a later date, but I've started a typescript definition file for this project. The definition file is incomplete and might not be perfect as I am not intimately familiar with all the shapes in this library yet. But to whomever it helps, you can plop this file in your project and start using bonescript in TS (more easily than without).
Save as
BoneScript.d.ts
in your project:To whomever is more familiar with the shapes in this library than I, please give me feedback or fill in the missing/improper shapes.
Copied from original issue: jadonk/bonescript#151