Zenorocha:clipboard 1.5.12 unusable even in fresh app


I’m trying to debug this with the package’s author, but I don’t know what to do.

The issue is open here:

It happens even when doing

$ meteor create testclip
$ cd testclip
$ meteor add meteor add zenorocha:clipboard
 => Errors while adding packages:

While checking for zenorocha:clipboard@1.5.12:
error: No compatible binary build found for this package. Contact the package author and ask them to publish it for  your platform.

Can somebody help?



Do you know if the package author published their package using the publish-for-arch option? If not have them try that first.

Builds an already-published package for a new platform.

Usage: meteor publish-for-arch packageName@version

When you publish a package with ‘meteor publish’ for a package which has
platform-specific components (eg, npm modules with native code), the package
will only be usable on machines of the same architecture that you are currently
on. To make your package’s version usable on other architectures, you can use
the publish-for-arch command. (The architectures currently supported by Meteor
are 32-bit Linux, 64-bit Linux, and 64-bit OS X; the ‘meteor deploy’ servers use
64-bit Linux.)

On a machine of the appropriate architecture, install Meteor and run
$ meteor publish-for-arch packageName@version

You don’t need to have a copy of your package’s source to do this: Meteor will
automatically download your package’s source and dependencies from the package


thanks for the input @hwillson.
The thing is this package has no arch-specific code: it’s a plain browser package,
see the package.js.
And if he does this, he’ll have to do it for all supported platforms, won’t he ?


Okay, then maybe there was an issue while publishing the package. As a work around though (that works - I just verified), you could always install/add a copy of the package locally:

mkdir APP_ROOT/packages; cd APP_ROOT/packages
git clone https://github.com/zenorocha/clipboard.js.git
cd APP_ROOT; meteor add zenorocha:clipboard


I had the same issues and pinned clipboard at 1.5.10 instead.

You can also add it as an npm module now.


thanks @hwillson, @elie : I’m covered if I decide to stick with the older version, jump to the new one, switch to the npm dep.

Do you know who to contact to get it properly fixed, though?


Take @hwillson’s advice. Or just stay at the previous version and wait for an update by the package author. I can’t imagine there’s something in the newest version that is essential for you.


I’ve switched to the npm module.