thelinmichael / spotify-web-api-node Goto Github PK

While the the access-token-using-client-credentials.jsexample works fine at version 2.3.1, it won't run on 2.3.6 (400 Bad Request).
I suspect this is related to superagent usage.
Cheers

As we can see in the api docs, we should not encode the colons which separate the query fields (artist, track, album etc)
https://developer.spotify.com/web-api/search-item/

The searchTracks() example from the main page call this url (with 'artist:Love')
https://api.spotify.com/v1/search?query=artist%3ALove&offset=0&limit=20&type=track
It should be https://api.spotify.com/v1/search?query=artist:Love&offset=0&limit=20&type=track

Otherwise the returned results aren't correct.

Hey

I'm trying to add 100 tracks to a playlist but the url is too long and fails. 414 - Request-URI Too Long
The API documentation say that you can post the tracks in the body instead the query string. Maybe it would fix this?

[s]

The call only works when the list of track URIs is passed in as a string.

Hi!
The GetTracks API should have an option to make the call with slices of 50 tracks (max) and give the result back.

When the replaceTracksInPlaylist method is invoked, Spotify returns an error that the request is missing a range_start parameter. Looking at the Spotify API documentation on replace a playlist's tracks, it would not appear that this field is required, except that it's actually using the same endpoint (https://api.spotify.com/v1/users/{user_id}/playlists/{playlist_id}/tracks) as reorder tracks, for which range_start is a required param.

The fix would likely be to add a range_start parameter (hard-coded to 0?) to the body of the post.

spotifyApi.replaceTracksInPlaylist(userId, playlistId, trackIds)

{ [WebapiError: Missing range_start parameter]
name: 'WebapiError',
message: 'Missing range_start parameter',
statusCode: 400 }

There are 2 uses of the "Remove tracks from a playlist" endpoint that are not covered by the wrapper:

• Removing a specific occurrence of a track
• Removing the track at a given position in a specific playlist snapshot

Accidentally hit submit

According the spotify API, snapshot_id is not mandatory. It seems to be in this interface, though. Is there a reason? If so, how do you retrieve a snapshot_id for a playlist?

with 2.3.2 I would receive a blank error message when calling authorizationCodeGrant as a promise. 2.3.1 works fine.

this.createPlaylist = function(userId, playlistName, callback) {...}

Needed for setting public as demonstrated in the examples.

I was wondering if the ability to access older states of a playlist (eg. Discover Weekly) is implemented.

I'm aware of this IFTTT applet, but if I understand this correctly, it works from the point you enable it forward.

So, can I access older snapshot_ids?

Apologies if this sounds like a stupid question, but how would I use access/refresh tokens in my app to authenticate a user or send a user to the authorise URL?

https://github.com/benchmarkstudios/slackbox/blob/master/app.js

If I run auth() instead of findTrack('track') on initialisation (Line 42), I get an authorisation URL in the console, which in turns gives me a code. If I paste this in to Line 9 and re-run - then the app works as needed.

However, if I try and run this again, obviously code becomes invalid and I have to repeat the process again, which isn't ideal, so I'm just wondering where I might be going wrong?

Any help appreciated!

At the moment there is no possibility to fetch the Retry-After response header if there was an error 429 (rate limiting). This information would be needed to develop a resume/retry logic.

I'm having some issues where it would be nice to see more details about the http requests and responses to the Spotify API. For instance, WebapiError looks like:

{
    "name": "WebapiError",
    "message": "Unauthorized",
    "statusCode": 401
  }

However, when I add an additional line of logging here:

/* Create an error object from an error returned from the Web API */
var _getErrorObject = function(defaultMessage, err) {
  console.log('got err', JSON.stringify(err, null, 2));

I get:

{
  "error": {
    "original": null,
    "response": {
      "req": {
        "method": "PUT",
        "url": "https://api.spotify.com/v1/me/albums",
        "data": "\"5XNpjmlGWc9XzX1XjH5lv7\"",
        "headers": {
          "user-agent": "node-superagent/2.3.0",
          "content-type": "application/json"
        }
      },
      "header": {
        "server": "nginx",
        "date": "Sun, 13 Nov 2016 15:43:39 GMT",
        "content-type": "application/json",
        "transfer-encoding": "chunked",
        "connection": "close",
        "www-authenticate": "Bearer realm=\"spotify\"",
        "access-control-allow-origin": "*",
        "access-control-allow-methods": "GET, POST, OPTIONS, PUT, DELETE",
        "access-control-allow-credentials": "true",
        "access-control-max-age": "604800",
        "access-control-allow-headers": "Accept, Authorization, Origin, Content-Type",
        "content-encoding": "gzip"
      },
      "status": 401,
      "text": "{\n  \"error\": {\n    \"status\": 401,\n    \"message\": \"No token provided\"\n  }\n}"
    },
    "status": 401
  }
}

This additional information would be useful! 😄

I'm following the code in the example and using express ... when receive the callback from spotify, I call the following function

app.get('/auth/spotify/callback',
  function(req, res){
    // The request will be redirected to spotify for authentication, so this
    // function will not be called.

    /* Read query parameters */
    var authorizationCode  = req.query.code; // Read the authorization code from the query parameters
    var state = req.query.state; // (Optional) Read the state from the query parameter

    console.log('authorizationCode ' + authorizationCode);
    console.log('state ' + state);

    spotifyApi.authorizationCodeGrant(authorizationCode)
      .then(function(data) {

        // Set the access token and refresh token
        console.log('The token expires in ' + data['expires_in']);
        console.log('The access token is ' + data['access_token']);
        console.log('The refresh token is ' + data['refresh_token']);

        spotifyApi.setAccessToken(data.body['access_token']);
        spotifyApi.setRefreshToken(data.body['refresh_token']);

        res.redirect('/home');

        // Save the amount of seconds until the access token expired
        tokenExpirationEpoch = (new Date().getTime() / 1000) + data.body['expires_in'];
        console.log('Retrieved token. It expires in ' + Math.floor(tokenExpirationEpoch - new Date().getTime() / 1000) + ' seconds!');
      }, function(err) {
        console.log('Something went wrong when retrieving the access token!', err.message);
        //res.redirect('/home');
        console.log('Something went wrong when retrieving the access token!', err);
      });
  });

I've tripple checked that the URI is actually added to the whitelist and that I am setting it when I instantiate everything

var spotifyApi = new SpotifyWebApi({
  clientId : client_id,
  clientSecret : client_secret,
  redirectUri : 'http://www.example.com/callback'
});

I can't figure out for the life of me why it keeps throwing this error

 name: 'WebapiError',
  message: 'invalid_grant: Invalid redirect URI',
  statusCode: undefined }

Calling getRecomendations from the example in source code throws an error. In the example below, getAudioFeaturesForTracks will return a valid response while getRecommendations will return the following err:

{ [WebapiError: invalid request]
  name: 'WebapiError',
  message: 'invalid request',
  statusCode: 400 }

spotifyApi.clientCredentialsGrant()
  .then(function(data) {
    console.log('The access token expires in ' + data.body['expires_in']);
    console.log('The access token is ' + data.body['access_token']);

    // Save the access token so that it's used in future calls
    spotifyApi.setAccessToken(data.body['access_token']);
  }, function(err) {
        console.log('Something went wrong when retrieving an access token', err);
  })
  .then(function(){
    spotifyApi.getAudioFeaturesForTracks(['38P3Q4QcdjQALGF2Z92BmR', '2HO2bnoMrpnZUbUqiilLHi']).then(function(data){
      console.log(data.body.audio_features)
    }, function(err){
      console.log(err)
    })
    spotifyApi.getRecommendations({ min_energy: 0.4, seed_artists: ['6mfK6Q2tzLMEchAr0e9Uzu', '4DYFVNKZ1uixa6SQTvzQwJ'], min_popularity: 50 })
      .then(function(data) {
        console.log(data);
      }, function(err) {
        console.log(err);
      });
  });

I know with one of my friends packages the README.md file was not distributed to NPM. Some bug in NPM. Just noticed this package does not have a README on NPM either.

When the the server has been running for a while and you call spotifyApi.SearchTrack() it returns
{ [WebapiError: Unauthorized] name: 'WebapiError', message: 'Unauthorized', statusCode: 401 }
It starts working again if the server is restarted. Any idea why this is happening?

Currently the promise for errors returns a string as an error, e.g.

err = {
  "error": {
    "status": 401,
    "message": "The access token expired"
  }
}

Can we have this wrapped in a try/catch block to parse as JSON?

Maybe get some inspiration from the node-sincerely or other API wrappers I've built.

Also I think that err should just be the error message, and then you should have a response perhaps with the actual JSON response.

Hello,
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

Hi there.

I'm trying to authorize my Spotify account using you're example code as shown below:

var credentials = {
  clientId : 'someClientId',
  clientSecret : 'someClientSecret',
  redirectUri : 'http://www.michaelthelin.se/test-callback'
};

var spotifyApi = new SpotifyWebApi(credentials);

// The code that's returned as a query parameter to the redirect URI
var code = 'MQCbtKe23z7YzzS44KzZzZgjQa621hgSzHN';

// Retrieve an access token and a refresh token
spotifyApi.authorizationCodeGrant(code)
  .then(function(data) {
    console.log('The token expires in ' + data.body['expires_in']);
    console.log('The access token is ' + data.body['access_token']);
    console.log('The refresh token is ' + data.body['refresh_token']);

    // Set the access token on the API object to use it in later calls
    spotifyApi.setAccessToken(data.body['access_token']);
    spotifyApi.setRefreshToken(data.body['refresh_token']);
  }, function(err) {
    console.log('Something went wrong!', err);
  });

But I can't seem to pass the authorizationCodeGrant part.

    this.spotifyApi = new SpotifyWebApi({
      clientId : '1234567',
      clientSecret : '8901234',
      redirectUri : 'http://localhost:6001/cv'
    });

    const scopes = ['user-read-private', 'user-read-email'];
    const state = '34fFs29kd09';

    const authorizeURL = this.spotifyApi.createAuthorizeURL(scopes, state);
    console.info(authorizeURL);

    this.spotifyApi.authorizationCodeGrant(code)
      .then(function(data) {
        console.log('The token expires in ' + data.body['expires_in']);
        console.log('The access token is ' + data.body['access_token']);
        console.log('The refresh token is ' + data.body['refresh_token']);

        // Set the access token on the API object to use it in later calls
        this.spotifyApi.setAccessToken(data.body['access_token']);
        this.spotifyApi.setRefreshToken(data.body['refresh_token']);
      }, function(err) {
        console.log('Something went wrong!', err);
      });

The URL given made my authorize and I've accepted. From there I'd get a new extremely long code:
12345678901§2345678901234567890&state=34fFs29kd09

Of course my code is different, but I don't know exactly if I'll have to use this code with or without the state parameter to the authorizationCodeGrant function.

this.spotifyApi.authorizationCodeGrant is not a function

As my title suggests I can't seem to use the function authorizationCodeGrant as it says it does not exists. Any idea whats up?

I have the code after accessing the authorizeURL but when I try to set the code on the api I get the following exception:

spotifyApi.authorizationCodeGrant is not a function TypeError: spotifyApi.authorizationCodeGrant is not a function

I cannot find the method in the console either. Did the API change?

We should add support for these endpoints -> https://developer.spotify.com/web-api/web-api-connect-endpoint-reference/

Hi,

I'm trying to use the search() method and it basically gives me a mostly empty object.
This is what I get:

{ tracks:
   { href: 'https://api.spotify.com/v1/search?query=Du+bist+sch%C3%B6n&offset=1&limit=1&type=track',
     items: [ [Object] ],
     limit: 1,
     next: 'https://api.spotify.com/v1/search?query=Du+bist+sch%C3%B6n&offset=2&limit=1&type=track',
     offset: 1,
     previous: 'https://api.spotify.com/v1/search?query=Du+bist+sch%C3%B6n&offset=0&limit=1&type=track',
     total: 2041 } }

Here's the code I'm executing with Git Bash (not gonna share my clientId and clientSecret of course, but they are there and correct):

var SpotifyWebApi = require('spotify-web-api-node');
var spotifyApi = new SpotifyWebApi({
    clientId: <clientID>,
    clientSecret: <clientSecret>,   
        redirectUri: 'http://localhost:8888/callback',
});
spotifyApi.search('Du bist schön', ['track'], { limit : 1, offset: 1}, function(err, data) {
    if (err) {
        console.error(err);
    } else {
    console.log(data.body)
    }
});

If I try this data.body["tracks"] it gives me more information:

{ href: 'https://api.spotify.com/v1/search?query=Du+bist+sch%C3%B6n&offset=0&limit=1&type=track',
  items:
   [ { album: [Object],
       artists: [Object],
       available_markets: [Object],
       disc_number: 1,
       duration_ms: 228213,
       explicit: false,
       external_ids: [Object],
       external_urls: [Object],
       href: 'https://api.spotify.com/v1/tracks/5PJeAJAw8YFUesmwARqn9Y',
       id: '5PJeAJAw8YFUesmwARqn9Y',
       name: 'Du bist schön',
       popularity: 68,
       preview_url: 'https://p.scdn.co/mp3-preview/04b971fb3e032f162d0096e442073a25c085cfb6',
       track_number: 11,
       type: 'track',
       uri: 'spotify:track:5PJeAJAw8YFUesmwARqn9Y' } ],
  limit: 1,
  next: 'https://api.spotify.com/v1/search?query=Du+bist+sch%C3%B6n&offset=1&limit=1&type=track',
  offset: 0,
  previous: null,
  total: 2041 }

but that's still not everything, as you can see. I tried using an access token (I have another function that gives me the audio features of a song) but I get the same result. I also tried using promises but still the same.
What am I doing wrong here? Please keep in mind that I'm fairly new to JavaScript and Node.
Also I do not really need everything, mostly I'd like to get the artist, name of the track and the id. How do I get only these things?

Hi there,

I'm trying to make a request, but I really don't get what I'm doing wrong, error messages like shown below keep showing up:

Something went wrong on auth! { [WebapiError: Bad Request] name: 'WebapiError', message: 'Bad Request', statusCode: 400 }

and

Something went wrong on playlists! { [WebapiError: Unauthorized] name: 'WebapiError', message: 'Unauthorized', statusCode: 401 }

This afternoon I got it working once, but now the access token is expired or something I guess? But when I'll run the refresh function you posted in the authorization section I'll get:

Could not refresh access token { [WebapiError: Bad Request] name: 'WebapiError', message: 'Bad Request', statusCode: 400 }

How can I debug this? What can I do?
If it helps, here is my SpotifyClient class:

import SpotifyWebApi from 'spotify-web-api-node';

class SpotifyClient {
  constructor(username) {
    this.username = username;

    this.spotifyApi = new SpotifyWebApi({
      clientId : 'CLIENT_ID',
      clientSecret : 'CLIENT_SECRET',
      redirectUri : 'http://localhost:6001/cv',
      accessToken : 'HERE_WAS_THE_CODE'
    });

    // this.setAuthorization();
    this.refreshAuthorization();
  }

  setAuthorization() {
    const scopes = ['user-read-private', 'user-read-email'];
    const state = 't3st';

    const authorizeURL = this.spotifyApi.createAuthorizeURL(scopes, state);
    console.log(authorizeURL);

    const code = 'HERE_WAS_THE_CODE_FROM_AUTH_URL';

    this.spotifyApi.authorizationCodeGrant(code)
      .then(function(data) {
        console.log('The token expires in ' + data.body['expires_in']);
        console.log('The access token is ' + data.body['access_token']);
        console.log('The refresh token is ' + data.body['refresh_token']);

        // Set the access token on the API object to use it in later calls
        this.spotifyApi.setAccessToken(data.body['access_token']);
        this.spotifyApi.setRefreshToken(data.body['refresh_token']);
      }, function(err) {
        console.log('Something went wrong on auth!', err);
      });
  }

  refreshAuthorization() {
    this.spotifyApi.refreshAccessToken()
      .then(function(data) {
        console.log('The access token has been refreshed!');

        // Save the access token so that it's used in future calls
        this.spotifyApi.setAccessToken(data.body['access_token']);
      }, function(err) {
        console.log('Could not refresh access token', err);
      });
  }

  getPlaylistById(callback) {
    console.info('spotify client get');

    this.spotifyApi.getPlaylist(this.username, '2tj5TA5I1QySyHI3YdpXYj')
      .then(function(data) {
        // console.log('Some information about this playlist', data.body);
        console.info('spotify client did return');
        // return data.body;

        callback(null, data.body);
      }, function(err) {
        console.log('Something went wrong on playlists!', err);
      });
  }
}

export default SpotifyClient;

• node: 6.6.0
• npm: 3.10.7
• spotify-web-api-node: 2.3.5

Test code

spotifyApi.getPlaylist(user, playlist, {
  offset: 5,
  limit: 10,
}).then((data) => console.log(data.body.tracks.next));

Current behaviour:

The above code logs the URL:

https://api.spotify.com/v1/users/{user}/playlists/{playlist}/tracks?offset=10&limit=10

Expected behaviour:

It should log following URL, confirmed via the Spotify Web API Console.

https://api.spotify.com/v1/users/{user}/playlists/{playlist}/tracks?offset=15&limit=10

Suggestion

Interestingly, the offset in the next URL appears to work. The offset parameter, however, seems to be ignored. I tried to find the issue myself, but no luck thus far.

My guess is that the offset parameter is accidentally omitted when an URL is generated.

The docs should say the track strings takes in URIs not IDs

I'm trying to create a playlist but I need to authenticate. I'm using the client credentials grant.

I'm able to get the access token, but authorizationCodeGrant is failing when I pass the token in. How should I change this so that authorizationCodeGrant works? Is this the correct way to be creating a playlist?

// Create the api object with the credentials
var spotifyApi = new SpotifyWebApi({
  clientId : config.spotifyid,
  clientSecret : config.spotifysecret
});

// Retrieve an access token.
spotifyApi.clientCredentialsGrant()
  .then(function(data) {
    console.log('The access token expires in ' + data.body['expires_in']);
    console.log('The access token is ' + data.body['access_token']);

    // Save the access token so that it's used in future calls
    spotifyApi.setAccessToken(data.body['access_token']);
    const authorizationCode = data.body['access_token'];

	  spotifyApi.authorizationCodeGrant(authorizationCode)
	  .then(function(data) {
	    // spotifyApi.setAccessToken(data.body['access_token']);
		return spotifyApi.createPlaylist('kabirvirji', 'My Cool Playlist', { 'public' : false })
		  .then(function(data) {
		    console.log('Created playlist!');
		  }, function(err) {
		    console.log('Something went wrong!', err);
		  });
		}, function(err) {
			console.log('authorizationCodeGrant error', err);
		});

// This is the error being thrown
  }, function(err) {
        console.log('Something went wrong when retrieving an access token', err);
  });

When running the getRecommendations function using the wrapper, an error is returned saying it is an invalid request. Turns out, it's because the seed_artists, seed_genres, and seed_tracks are being sent as arrays in the query string rather than comma separated strings. This is simply solved by adding .join(',') on the end of the arrays that are sent, but this isn't specified in the docs. Please either update the dogs or have the arrays turned into strings automatically. That would have saved me a lot of headache.

Hey,

I'm having issues using the refresh token to get a new access token. Is there anythign I need to do besides using the setRefreshToken method?

Thanks,

Tom

I'm trying to get tracks from playlist that is longer than 100 tracks and there is a limit of a 100. I tried changing setting {limit : x, offset: x}, but it seems not working.

I'm using Node version 5.5.0, and spotify-web-api-node version 2.3.0. I'm using the following function to get the playlists from my own Spotify account.

var SpotifyWebApi = require('spotify-web-api-node');
var clientId = '<client id>';
var clientSecret = '<client secret>';

var spotifyApi = new SpotifyWebApi({
    clientId: clientId,
    clientSecret: clientSecret
});

function getUserPlaylists(userId) {
    spotifyApi.clientCredentialsGrant()
        .then(function(data) {
            spotifyApi.setAccessToken(data.body['access_token']);
            spotifyApi.getUserPlaylists(userId)
                .then(function(data) {
                    console.log(data);
                }, function(err) {
                    console.log('Something went wrong!', err);
                });
        }, function(err) {
            console.log('Something went wrong when retrieving an access token', err);
        });
}

However, whenever I call this function with my own Spotify user ID (I signed up with Facebook), I get the following error: Something went wrong! { [WebapiError: Not found.] name: 'WebapiError', message: 'Not found.', statusCode: 404 }. Other API functions work still, but all of a sudden this one ceased to work even though I haven't touched my server or the code for my server since it was working well. I checked the endpoints in the spotify-web-api-node source code and they seem to still be correct for getUserPlaylists.

We have a auth flow where our android app send the auth code to the server, and server makes a authorizationCodeGrant api call to get the accessToken and refreshToken, currently the call is timing out. Is this a correct flow and is it suppose to work, note that the redirect URI on android is not a http url but a custom scheme.

Title says it all, what do you think? I can probably make this change.

This example does not work. It causes a Bad Request.

var tracks = { tracks : [{ uri : "spotify:track:4iV5W9uYEdYUVa79Axb7Rh" }] };
var options = { snapshot_id : "0wD+DKCUxiSR/WY8lF3fiCTb7Z8X4ifTUtqn8rO82O4Mvi5wsX8BsLj7IbIpLVM9" };
spotifyApi.removeTracksFromPlaylist('thelinmichael', '5ieJqeLJjjI8iJWaxeBLuK', tracks, options)
  .then(function(data) {
    console.log('Tracks removed from playlist!');
  }, function(err) {
    console.log('Something went wrong!', err);
  });

The issue lies with the tracks variable, which is not in the correct format.

Should be:

var tracks = [{ uri : "spotify:track:4iV5W9uYEdYUVa79Axb7Rh" }];

I verified this after taking a look at the source code

removeTracksFromPlaylist: function(userId, playlistId, tracks, options, callback) {
    var request = WebApiRequest.builder().
      withPath('/v1/users/' + encodeURIComponent(userId) + '/playlists/' + playlistId + '/tracks').
      withHeaders({ 'Content-Type' : 'application/json' }).
      withBodyParameters({
        'tracks': tracks // the object is being created here
      })

I suppose you would have to change the docs and not the input as this would be a breaking change.

not a huge deal, but i had to dive into the code to find this one:

line 1096

  /**
   * Reorder tracks in a playlist.
   * @param {string} userId The playlist's owner's user ID
   * @param {string} playlistId The playlist's ID
   * @param {int} rangeStart The position of the first track to be reordered.
   * @param {int} insertBefore The position where the tracks should be inserted.
   * @param {Object} options Optional parameters, i.e. range_length and snapshot_id.
   * @param {requestCallback} [callback] Optional callback method to be called instead of the promise.
   * @returns {Promise|undefined} A promise that if successful returns an object containing a snapshot_id. If rejected,
   * it contains an error object. Not returned if a callback is given.
   */
  this.reorderTracksInPlaylist = function(userId, playlistId, rangeStart, insertBefore, options, callback) {
  }

it would be great to have the documentation include this function for future users.

Accessing response headers is important to be able to handle caching. Therefore, make the headers optionally available in all responses.

Hello -- I am going to use this module heavily and so I think it'd be great if we could be collaborators on this project both on GitHub and NPM. Double whammy power. Would you be open to sharing access?

I'm looking at iterating through a list of tracks in a playlist. The limit is set at 20 right now. How do I use this framework to iterate through all records? Could you point me towards an example?

Thanks!

In this request https://api.spotify.com/v1/users/spotify_españa/playlists/6WCc127FLZ5hztL9gpFT3j the playlist owner spotify_españa has an accented character, when passed through the library this causes a 400 response due to the character encoding of that string. I'm currently mitigating this by callingencodeURIComponent(<playlist owner>) before calling getPlaylist - but really this should be handled by spotify-web-api-node.

Node.js Command prompt output

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "spotify-web-api-node" "--save"
npm ERR! node v4.4.7
npm ERR! npm v2.15.8
npm ERR! file C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch\package.json
npm ERR! code EJSONPARSE

npm ERR! Failed to parse json
npm ERR! Trailing comma in object at 6:1
npm ERR! }
npm ERR! ^
npm ERR! File: C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch\package.json
npm ERR! Failed to parse package.json data.
npm ERR! package.json must be actual JSON, not just JavaScript.
npm ERR!
npm ERR! This is not a bug in npm.
npm ERR! Tell the package author to fix their package.json file. JSON.parse

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch\npm-debug.log

C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch>npm install spotify-web-api-node
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "spotify-web-api-node"
npm ERR! node v4.4.7
npm ERR! npm v2.15.8
npm ERR! file C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch\package.json
npm ERR! code EJSONPARSE

npm ERR! Failed to parse json
npm ERR! Trailing comma in object at 6:1
npm ERR! }
npm ERR! ^
npm ERR! File: C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch\package.json
npm ERR! Failed to parse package.json data.
npm ERR! package.json must be actual JSON, not just JavaScript.
npm ERR!
npm ERR! This is not a bug in npm.
npm ERR! Tell the package author to fix their package.json file. JSON.parse

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch\npm-debug.log

npn-debug.log

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'spotify-web-api-node' ]
2 info using [email protected]
3 info using [email protected]
4 verbose install initial load of C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch\package.json
5 verbose stack Error: Failed to parse json
5 verbose stack Trailing comma in object at 6:1
5 verbose stack }
5 verbose stack ^
5 verbose stack at parseError (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:390:11)

5 verbose stack at parseJson (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:79:23)
5 verbose stack at C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:48:5
5 verbose stack at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:78:16
5 verbose stack at FSReqWrap.readFileAfterClose as oncomplete
6 verbose cwd C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch
7 error Windows_NT 10.0.14393
8 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "spotify-web-api-node"
9 error node v4.4.7
10 error npm v2.15.8
11 error file C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch\package.json
12 error code EJSONPARSE
13 error Failed to parse json
13 error Trailing comma in object at 6:1
13 error }
13 error ^
14 error File: C:\Users\Broccoli-GO\Desktop\scripts\bots\twitch\package.json
15 error Failed to parse package.json data.
15 error package.json must be actual JSON, not just JavaScript.
15 error
15 error This is not a bug in npm.
15 error Tell the package author to fix their package.json file. JSON.parse
16 verbose exit [ 1, true ]

Is there a way to ge a list of all spotify locale's?

Thanks!

Tom

i was developing one app to follow me by others and facing some issues on ios and IE11.

ios issue : unable get authentication...when ever i am clicking the authentication button to follow me, nothing is happening.but this works fine on android chrome firefox. When i add "/?" at the end of redirect URI, it will works fine.pls help on this.

IE11 issue....i am unable to follow anyone when i am using IE11.i guess promises function are not working on IE11....pls help onthis too..

Thanks !

Hi guys,
on the spotify api guide there is the "Client Credentials Flow" for authorizing with the client id and client secret only. Is there a way to do this with the web api node?
Why: I'm using the spotify api server side so I don't have a redirect URL.
Best regards,
Fabian

After my access token expires I get an error saying 'Unauthorized.' This is expected since my token has expired, but is there a way to check on the expiration status of the token to see if we need to refresh it before the request is made? I was thinking I could calculate the expiration datetime when first receiving the token and check before each request to see if it's past that time, but wondering if this was built in already. Thanks!

Superagent uses a browser property in its package.json to provide a different entry point to the library when bundling for browser use. This is great, since it prevents browserify from bundling the implementation to make requests using node.

It turns out that the browser property is not transitive. Thus, a project importing spotify-web-api-node and using webpack/browserify to bundle, will bring that node code together. The resulting size of the spotify-web-api-node bundle is 90kB minified not-gzipped. Bundling just superagent results in 15kB, and this library shouldn't add too much on top of it.

We should expose a browser entry point in the package.json file for this project that points to the browser implementation of superagent, or find out a way to make the property transitive.