Open
Conversation
Dynamically find version of package.json Update readme for new installation/run instructions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I did this before realizing Google DOES NOT support Play Music with OAuth 2.0 despite Client Login being deprecated last year... Based on some research I did, the music manager app uses OAuth 2.0 but the website still only supports Client Login.
I implemented this using Google's official OAuth API for node google-apis-node-client. I put it here thinking it would be helpful since Google has deprecated Client Login and its retirement could be coming very soon. Added bonus people won't be exposing their master Google password to use this.