Closed smwhr closed 3 years ago
Hooray!
I think probably the most stable thing is to have a redundant duplicate of the same inklecate within the inkjs-comaptible folder. Seems a little silly and wasteful, but it's no worse than it is right now, and it means that when eventually break compatibility again, we don't have to think too hard to do the right thing.
Version of inkjs that supports v1.0.0 of ink is almost ready ! 🥳
I'm preparing a PR with the following
I was wondering if you wanted to
inkJsCompatible
variable in placeinkjs-compatible
inklecate
binaries to deal with future incompatibilities without having to do the plumbing again. Or if you'd rather clean all up. Let me know !