-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Published to NPM? #38
Comments
Not yet. Will likely be published at the end of the month I've been told. In the meantime I you can run ./build/all.sh and utilize the index.js generated file in your project. This file will export all the classes you need. |
Alright, thanks. I can wait. Building it manually makes it a bit awkward to maintain in our project. So anything on master that is not on 1.2.x is for the next minor release and only gets published to npm when that release happens? Essentially I'm waiting for 1.3 then? Is that right? |
I believe so. I'm in a similar boat with my project. For now I have just created a "vendor/shaka-player" folder in my root dir and placed the compiled index.js there. Once the NPM dependencies are available I'll swap that out with a normal node_modules include. Not ideal but works fine. |
Yes, Jason has the right of it. We'll be releasing these changes in 1.3.0. 1.2.x is collecting bugfixes only. We expect 1.3.0 out by the end of the month, and we'll update the milestones page if that changes. |
Great, thanks guys. |
Have the latest change to master been published to npm? Updating/Installing through npm is not picking up the latest changes.
The text was updated successfully, but these errors were encountered: