Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Do you need someone to take over the project?
See original GitHub issueFrom looking at the Git branches, there was work done to create a newer version in 2017. This work was never completed, and any merged pull request since 0.8.0 haven’t been deployed to npm.
I use this software to control the lights on my home network and still think it’s the best solution out there. Sadly, without these changes, updates, and security fixes, the library will eventually become useless.
Either I could take over this project myself, or I could create my own. You’ve gone through a considerable effort building out this library, I think rewriting it myself would be a waste of time when you’ve already produced a substantial amount of work.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Myself, I have moved to the https://github.com/futomi/node-lifx-lan package . It support promises, and is much faster when updating lights.
Turning multiple lights on simultaneously with the node-lifx package ended up with delay between each light for me. With node-lifx-lan, I have no such issue.
Actually here, it’s done: https://github.com/node-lifx/node-lifx-rebirth
@ristomatti Invited you to the GitHub org node-lifx. There are two PRs to merge. One is your es2015-dev branch and the other is one where I updated all npm vulnerable dependencies.
If those get merged into master, I’ll go ahead and deploy version 1.0.0 to npm.