Using this within Firefox gives the following error: Uncaught ReferenceError: setImmediate is not defined
According to these documentation this is a non-standard feature. In fact most-likely no browser (except MS Edge) supports it.
So I wonder if this problem could be solved using something else like plain setTimeout. Thanks for any feedback. 🙃

Many thanks for your example that shows how to navigate through a playlist.

But unfortunatly the complicated thing seems for me how to create a playlist.
I think that "Browse" is simpler than "Search". Therefore the example should show how to
call "Browse" with a given url for a local directory that contains an album with some songs.
Then the result of Browse should be loaded into a playlist and should start to play the songs.

Many thanks for your support.

If you use autoConnect: false in the constructor of Mopidy and then call close on the instance without connecting, the following error is thrown:

TypeError: Cannot read property 'close' of null
    at Mopidy.close (/.../node_modules/mopidy/src/mopidy.js:166:20)

Hello,
I would be interested in adding an event advertising the number of pending requests, at emission and reception of a message.
This would allow clients to easily know if there are pending requests going on.

I have added
this.emit("requests:count", Object.keys(this._pendingRequests).length)
after the lines 109 and 181 of mopidy.js, this seems to do the trick.

Hi,

Is there any way of getting the list of all possible events from the server?

To get all methods, we can do a {method: 'core.describe'} call. Is there a way to do the same thing with events, e.g. a {method: 'core.CoreListener.describe'} call?

Hi,

I installed mopidy.js like this: npm i mopidy.

Then I try to import and use Mopidy in my Vue3 project like this:

import Mopidy from 'mopidy'
const mopidy = new Mopidy()

I get the following error in the console:

Uncaught TypeError: EventEmitter is not a constructor
    js mopidy.js:10
    __require chunk-XNAE4CLY.js:7
    <anonymous> mopidy:1
mopidy.js:10

What am I doing wrong here?

I arrived on this project through a problem I'm having with node-red-contrib-mopidy (cf #42 ) and I realise this might also be used with https://github.com/jaedb/iris which I also use, so thanks again !

It would be nice to have a list of projects that use mopidy.js in the README, also enabling developers to see how it is being used (in my usecase trying to find example code for tracklist.add)

The release of Mopidy.js 1.0 is getting nearer. Due to the amount of changes in Mopidy.js since v0.5, I'd like to get some pre-release testing by existing Mopidy web clients before pushing a release to npm.

To build a single JS file to test with:

1. clone the mopidy.js git repo,
2. run yarn to install dependencies and then
3. run yarn build to build dist/mopidy.js.

All breaking changes are documented in the changelog.

@tkem Do you have time to try Mopidy.js' master branch with Mopidy-Mobile?

@kingosticks @jcass77 Does any of you have time to try Mopidy.js' master branch with Mopidy-Musicbox-Webclient?

@jaedb Do you have time to try Mopidy.js' master branch with Mopidy-Iris?

I'm running Mopidy 1.0.0 and using latest mopidy.js build.

m = new Mopidy();
m.history
Object {getLength: function, getHistory: function}
m.history.getLength()
Server returned error: Object {message: "Method not found", code: -32601, data: "Object mounted at "core.history" has no member "get_length""}

The same error is returned for history.getHistory()

Related to "solving" mopidy/mopidy#434 - Idea is to take care of all the making sure we account for timeouts running over and using animation frames so we get more accurate timing and don't get updated when the tab isn't visible.

http://jsfiddle.net/deqfpk8x/9/ has a quick prototype for this.

Just tried to require Mopidy with React Native and hit an issue with when package not working with React Native's package manager.

I solved this by adding following npm-shrinkwrap.json to my project:

{
  "dependencies": {
    "when": {
      "version": "3.7.7",
      "from": "[email protected]",
      "browser": false
    }
  }
}

Read more: cujojs/when#484 (comment)

Just something you might want to look into.

Disclaimer: I'm not that much of a JS guru, so if I'm completely wrong on this issue or there are already much easier ways to do what I'm trying to achieve, I'd be glad to be corrected or pointed to the right direction...

The when.js CommonJS Promises/A implementation used by mopidy.js provides some useful "static" methods, which are not available easily through the mopidy.js interface. I especially like to use when.all() and/or when.join(), which somewhat resemble pykka.join(), which I like ;-)

I currently use what I consider a very ugly hack to get that functionality without loading when.js seperately, to do something like this:

var all = mopidy.getVersion().__proto__.constructor.all;
return all([
  mopidy.tracklist.getConsume(),
  mopidy.tracklist.getRandom(),
  mopidy.tracklist.getRepeat(),
  mopidy.tracklist.getSingle()
]).then(function(results) {
  return {
    consume: results[0],
    random: results[1],
    repeat: results[2],
    single: results[3]
  };
});

Now, it would be nice if all and/or the similar when.join() would be exposed by Mopidy directly, since I think this use case might not be uncommon for clients. I guess all could be easily added as a property to either the Mopidy constructor or a mopidy instance.

As stated before, I don't know if there's an easier or cleaner way to achieve this. However, what I don't want to do is add another

<script src="when.js">

since the functionality is already there...

"mopidy": "^0.5.0"

So when calling with:
mopidy.library.getImages(['spotify:artist:4FCGgZrVQtcbDFEap3OAb2'])

I get the message:
Expected a list of URIs, not u\'spotify:artist:4FCGgZrVQtcbDFEap3OAb2\' back.

Looking at the documentation this looks like the correct way to call the function? Have I understood correctly?

PS I have made the same call with:
mopidy.library.getImages({ uris: ['spotify:artist:4FCGgZrVQtcbDFEap3OAb2']})

I don't get an error, but have never got any images back (That could be a mopidy-spotify thing.

mopidy.js is great as a starter to build an own JS user interface. I think it would be even greater for JS developers to have an example mopidy plugin they can utilize.

Have a basic mopidy plugin (within examples) which servers the web files within the mopidy process. Only change the plugin name, drop your web files (HTML, CSS, JS, etc) in a dedicated folder, ready to go.

Just an idea...

Cheers
bluepuma

I'm logging all events, like:

mopidy.on(function (ev, args) {
  console.log(ev);
});

When pause or play occurs I get event:playbackStateChanged, however when the music is stopped (by mopidy.playback.stop()) I don't get any event.

Hi, thanks for developing and maintaining mopidy.js, I use it almost daily through my nodered setup with https://github.com/emiloberg/node-red-contrib-mopidy/ and it works great !

I'm having trouble writing a function that loads 20 random tracks from my library as described in emiloberg/node-red-contrib-mopidy#11

I'm not sure what I'm doing wrong and I seem to have gone through a number of combinations ('uris', 'tracks', etc.) without success.

Any tips on how to tackle this problem ?

Node.js has a quite standardized event interface called EventEmitter. In browsers, the same interface is made available with the help of Browserify (or Webpack).

The EventEmitter API is quite similar to Bane.js, so replacing Bane.js with the far more widely used EventEmitter API should be quite straight forward. However, EventEmitter lacks a the .off() method from Bane.js, so this is a breaking change.

Tasks:

• Replace Bane.js with EventEmitter
• Test that Browserify makes EventEmitter available on the browser
• Update Mopidy's Mopidy.js docs

After getting the state:online event and calling...

mopidy.library.search({
  query: 'Newton Faulkner',
}).done(console.log.bind(console))

I'm getting this \'unicode\' object has no attribute \'items\ error sent back...

Server returned error: { message: 'Application error',
  code: 0,
  data: 
   { message: '\'unicode\' object has no attribute \'items\'',
     traceback: 'Traceback (most recent call last):\n  File "/usr/lib/python2.7/dist-packages/mopidy/internal/jsonrpc.py", line 133, in _handle_single_request\n    result = self._unwrap_result(result)\n  File "/usr/lib/python2.7/dist-packages/mopidy/internal/jsonrpc.py", line 222, in _unwrap_result\n    result = result.get()\n  File "/usr/lib/python2.7/dist-packages/pykka/threading.py", line 52, in get\n    compat.reraise(*self._data[\'exc_info\'])\n  File "/usr/lib/python2.7/dist-packages/pykka/compat.py", line 12, in reraise\n    exec(\'raise tp, value, tb\')\n  File "/usr/lib/python2.7/dist-packages/pykka/actor.py", line 201, in _actor_loop\n    response = self._handle_receive(message)\n  File "/usr/lib/python2.7/dist-packages/pykka/actor.py", line 295, in _handle_receive\n    return callee(*message[\'args\'], **message[\'kwargs\'])\n  File "/usr/lib/python2.7/dist-packages/mopidy/core/library.py", line 316, in search\n    query = _normalize_query(query or kwargs)\n  File "/usr/lib/python2.7/dist-packages/mopidy/core/library.py", line 358, in _normalize_query\n    for (field, values) in query.items():\nAttributeError: \'unicode\' object has no attribute \'items\'\n',
     type: 'AttributeError' } }

Is this something server side or am I messing up somewhere?

Cheers,

Ben

For hours I have been trying to get mopidy.js to run, my major challenges:

1. Does not build with node 15 (seems to work with 12 and 14)
2. Parcel needs to be installed
3. Changing the script to connect to remote mopidy
4. Configure mopidy to enable remote hosts to access
5. Finally "Uncaught (in promise) TypeError: track.artists is undefined"

It seems to work now, I play a radio stream on the Raspi3+ (latest Raspberry Pi OS Lite), can access remotely via Iris and mopidy.js seems to connect, I can see web socket messages. But the console shows the exception and it displays "Unknown - Unknown".

When I try to run the example code I get this.

Uncaught SyntaxError: Cannot use import statement outside a module (at web.js:4:1)
I've done npm install and npm test seems to run fine.
Then I pointed my browser to the HTML file and got the previous mentioned error. I also ran a simple python webserver to host the HTML and browsed to the port and got the same error. I'm trying to open web.html so I can access the console and play with the API.

I was working on a project that relied on Mopidy.js so I started writing a TypeScript definition file for the API. It is mostly done but I have some more urgent matters come up and am not going to be able to finish the definitions and submit them to DefinitelyTyped.

If anyone wants to pick up where I left off, I think there's <10% left to do, and the hard parts like the on/off event subscription API are already done. Just look for "@todo" comments in the code. Feel free to finish it and submit to DefinitelyTyped with your name instead of mine:

https://files.terriblefish.com/mopidyjs/index.d.ts

Mopidy.js 0.4.0 released 2014-06-24 added support for the by-position-or-by-name calling convention, but the by-position-only calling convention is still the default.

Short term we should change the default. Long term we should remove the by-position-only calling convention.

We can change this now, but then we should not bundle the new release of Mopidy.js with Mopidy, so we don't break old clients, ref. mopidy/mopidy#1460.

@jodal It looks like this commit seems to have broken things? unless it's just for me? This is change where the namespaces were switched from PascalCase to lowercase:

Lowercase namespace names

These are the lines in question:

• https://github.com/mopidy/mopidy.js/blob/master/src/mopidy.d.ts#L84
• https://github.com/mopidy/mopidy.js/blob/master/src/mopidy.d.ts#L594

ES6 has standardized the Promise object. Of the browsers supporting WebSockets, mostly everyone except IE10 and IE11 supports Promise.

Mopidy.js should replace the When.js dependency with ES6 Promises without any bundled polyfill, making it as small as possible by default. Clients that want Mopidy.js to work with IE10/IE11 should provide a Promise polyfill themselves.

Tasks:

• Remove Mopidy.when() reexport of When.js
• Replace When.js with ES6 Promise in browsers
• Replace When.js with "promise" npm package in Node.js
• Update Mopidy's Mopidy.js docs

As discussed in https://discuss.mopidy.com/t/unable-to-create-a-playlist-from-a-podcast-uri-in-mopidy-js/737, clients sometimes may want to create models by themselves, e.g. to add tracks to playlists. Currently, this is only possible by creating a plain JS object with the semi-documented __model__ property.
Although the use case discussed above concerns the playlist API, there may be other cases where creating models, especially Refs, may be desirable. So adding functionality to create these on the client in a way that's guaranteed to work with current and future versions of the API would be a welcome addition.

If the mopidy server is mounted in a subdirectory via a reverse proxy (e.g., https://domain/mydir, such that apps are available under https://domain/mydir/app), then the default websocket url in https://github.com/mopidy/mopidy.js/blob/master/src/mopidy.js#L65 points to the wrong location. Since the code already uses browserify (yey!), a solution is to use url.resolve() in order to determine the path:

var url = require("url");
var path = url.resolve(
    (typeof document !== "undefined" && document.location.pathname) || "/",
    "../mopidy/ws"
);

and then

settings.webSocketUrl = settings.webSocketUrl ||
    protocol + currentHost + path;

In my setup, mopidy is mounted in a subdirectory via nginx and it took me a while to figure out why moped wasn't able to connect to the websocket. The above change would make it work without any further configuration.

What do you think?

The main advantage of the Buster.js test framework is that the same test suite can be executed both on Node.js and in the browser. I believe the same is achievable with the Karma test runner together with the Mocha test framework.

Since Buster.js is barely maintained, Mopidy.js' test suite should be ported to Karma+Mocha.

When doing so, we can either keep referee for assertions through the use of karma-referee or rewrite them to use the Chai assertion library.