✅ [Feature Request] Envato Package Manager

Would love to see some kind of package management system for uploading item updates and / or publishing new items. Packaging in a .zip file is a huge pain both for us and for our customers, who could use a package management system for installing updates.

Something like npm, with features like:

  • envato publish (to upload the package)
  • envato clone (to download the package)
  • envato update (to update downloaded package to latest version)
  • .envatoignore (similar to .gitignore, to ignore files when uploading to envato

@Envato If you are willing to add such a feature, we would be more than willing to help you with the development.

@everyone like this post if you want this feature too

4 Likes

We’ve asked for at least API item updates like 5 years ago and again 2 years ago, and then we’ve stopped thinking this is more than an indie market.

Being a CodeCanyon author selling Node.js apps, I see the frustration of my buyers when they have to manually update files.

I see your point, however. It’s probably best if we develop the Envato Package Manager ourselves, rather than waiting for Envato.

Update: we started working on the Envato Package Manager ourselves.

Package envato-cli is currently available on npm. It uses our server to authenticate to Envato API.

Current features:

  • Run envato login to authenticate against Envato API.

  • Run envato check-purchase [purchase_code] or envato purchase [purchase_code] to verify one of your purchases, given the purchase code.

  • Run envato check-sale [purchase_code] or envato sale [purchase_code] to verify one of your sales, given the purchase code.

You can also use the alias epm: for example, you can run epm login.

Package envato-cli now supports the command envato archive.

  • Run envato archive to create a zip archive with the current folder. It will use version and name from package.json (from the current folder). You can add a .envatoignore file to ignore files and folders.

The Envato Package Manager is now live! As a reminder: items uploaded to EPM are hosted by us (Honeyside), not by Envato. At the moment, we do not collect usage data. Should we introduce data collection in the future, you will be promptly notified by the CLI itself.

EPM works in a very similar way to NPM, but every download (epm clone or envato clone) is authenticated against Envato API. You must be either in possession of a purchase code or be the author of an item, in order to clone that item. You must be the author of the item in order to publish or unpublish on EPM.

  • Run envato clone [item_id] [purchase_code] to download an item. The item must have been made available on EPM by its author.

  • Run envato clone [item_id] - to download an item if you are the author of such item (no purchase code required).

  • Run envato publish [item_id] to publish an item. The item must already have been approved by Envato. It must be available on at least one marketplace.

  • Run envato unpublish [item_id] to unpublish an item. You must own the item to remove it from EPM.

1 Like

Update (sorry for the delay, we were very busy): following complaint from Envato, we removed the “Envato Package Manager” from both npm and Github. We are very sorry but we do understand Envato’s point of view.

The package has now been renamed “Honeyside CLI” and the publish / clone feature has been removed. You can still login into Envato API, check sales and purchases and create an archive. .envatoignore file is now .honeyignore

Commands :

  • Run honey login to authenticate against Envato API.

  • Run honey check-purchase [purchase_code] or envato purchase [purchase_code] to verify one of your purchases, given the purchase code.

  • Run honey check-sale [purchase_code] or envato sale [purchase_code] to verify one of your sales, given the purchase code.

  • Run honey archive to create a zip archive with the current folder. It will use version and name from package.json (from the current folder). You can add a .envatoignore file to ignore files and folders.