Closed knocte closed 5 years ago
@danrobinson should I care rebasing this PR or will you keep not reviewing it?
This project is dead. You might want to fork it or take a look at Spedn and CashScript.
BCash? lol
Thanks for doing this—LGTM! If you don't mind rebasing it I can test it locally and then merge.
@danrobinson thanks for the feedback! I just rebased it.
@danrobinson ping?
Is there any more work that needs to be done before ivy-bitcoin 0.0.34 can be published on the npm registry? It would make it easier to test this out.
Published version 0.0.34.
@danrobinson The suggested changes were applied with the latest public ivy-bitcoin
package.
@danrobinson The suggested changes were applied
@danrobinson ping
@danrobinson ping
I ran npm update
in the ivy-compiler dir. This fixed the build errors I was seeing so I've added a commit with the updated package-lock.json
@danrobinson ping :)
@knocte How would you feel about outputting to stdout by default, rather than a file? I don't have a strong preference but it seems more Unix-y.
Otherwise looks good to me!
@danrobinson
Outputting to a file with a name based on the input file name is more compiler-y though. Not that I have a strong preference either.
Exactly, I don't know any unix-y compiler that outputs to stdout by default.
SGTM! Curious what you're planning to use this for. (Please don't use Ivy in production!)
@danrobinson Would it be possible to publish ivy-compiler as it's own npm package?
@canndrew You could go ahead and do that yourself, couldn't you? Not sure you need me
Input files can be in any extension, and the output will just be
sameFileName.tpl
.NOTE: chai and mocha were added as deps because otherwise it would throw: