-
Notifications
You must be signed in to change notification settings - Fork 26
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
Feature Request: Make project a global NPM package with cli #9
Comments
Good idea. I'll work on this since I'll have to register the package through NPM. |
Currently waiting to hear back from the owners of multicast on NPM. |
- added new preset channel listing when adding a new channel - upped font size for alerts (addresses #12) - conditionally includes Google's cast script only when displayed on receiver device (addresses #1) - added --serve-only flag to prevent interrupting devices while debugging - added multicast bin to package.json to simplify startup and prepare for NPM (see #9) - added new features to README - cleaned up code formatting
- bump major version - multicast can now be installed as a global NPM package (addresses #9) - added explanation when run with no arguments - added config interface for initial setup - check if cast is defined before referencing in client.js
Package is now available for install here via NPM. Let me know how it works for everyone. |
Welp, I found an issue with installing via NPM. When you are doing global NPM install, I don't think its a good idea to be using Gulp.
|
You could be right about avoiding Gulp, but I don't think that's the cause of the error. I added a potential fix for this in the README: Can't launch after installing via NPM? Make sure your export NODE_PATH=/opt/lib/node_modules
|
Sweet Deal. There are some other features I would like to add to the CLI but, for right now, this issue is fixed. |
There are several advantages of this:
Point being, This is where I think multicast should go. I can probably get started on a thing this weekend to merge in. No guarantees though.
The text was updated successfully, but these errors were encountered: