authorizationCodeGrant() is not included in the browser bundle
See original GitHub issueHello, I’m trying to authenticate an user but the resulting instance doesn’t have any of the server methods.
import SpotifyWebApi from 'spotify-web-api-node';
const credentials = {
clientId: `clientId`,
clientSecret: `clientSecret,`
redirectUri: 'http://localhost:3000/callback'
};
const SpotifyApi = new SpotifyWebApi(credentials);
...
SpotifyApi.authorizationCodeGrant(...code);
undefined
Issue Analytics
- State:
- Created 7 years ago
- Comments:6
Top Results From Across the Web
OAuth grant type parameters - 11.2 - Documentation
Indicates the type of grant being presented in exchange for an access token and possibly a refresh token. The value is an extensibility ......
Read more >spotifyApi.authorizationCodeGrant is not a function · Issue ...
When the instance is logged to the browser console, 'authorizationCodeGrant' does not appear as an available function for access.
Read more >NetSuite Applications Suite - Oracle Help Center
Authorization Code Grant Flow Error Messages in the Login Audit Trail. The following table lists errors that are visible in the Detail column...
Read more >Implementing the authorization code grant type | Apigee X
This grant type is intended for apps that are written by third-party developers who do not have a trusted business relationship with the...
Read more >Authorization Code Grant Type - SymfonyCasts
The only missing piece is OAuth: getting the access token for each user so that we can make an API request to count...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
And now it is explained in the README.
You should put that disclaimer in the readme. Anyway, I was just testing it locally and would not expose my secret…