-
Notifications
You must be signed in to change notification settings - Fork 40
Some updates required for use with Iniquity 3 #16
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
base: master
Are you sure you want to change the base?
Conversation
I also ported over the build.cmd and what not over to the more 'npm' way of doing things.
|
Thanks for these changes! At quick glance they look good, but I hope to have the time to take a closer look over the weekend. |
|
Very cool, no rush on my end :) I will say that fTelnet is a crucial part of iniquity 3. Thank you again for creating it. |
Hey Rick, any thoughts on my pull request? |
Hey Rick, it's been a long long while. Anyways, I've loved fTelnet for so long. Truly it's the best of its kind. Even cooler you're on github now, and, are all about TypeScript. Anyways, this adventure of mine began when I was wondering if I could just include fTelnet as an npm module in my project... and, from there I started expanding just a little in terms of its options. Just some things I needed. But now, this repo can be installed via npm. Also, there is a development server for easy testing fTelnet against. To be honest, I believe I could make it production quality if you're interested. Then fTelnet could maybe have the proxy and everything ready to go for people! Just ideas... let me know if anything I've done here is of interest to you.