Last release (v2.1.2) /js/ folder missing

[mateuszjarzewski]

Title tell the story.
https://github.com/moxiecode/plupload/archive/v2.1.2.zip

[jayarjo]

Binaries are in the attached archive (green one).

The one that you mention should include sources and doesn't. Weird. Thanks for letting us know.

[calmdev]

+1 I'm running into this issue installing from composer.

[jayarjo]

@calmdev, what's the point of installing this via composer anyway? I've merged the commit with composer.json, but it's still a bit of mystery to me. Is there any benefit? After all Plupload is not exactly a PHP package or anything ready to be used out of the box... Can you describe how do you use it?

[calmdev]

@jayarjo using composer as a web project dependency manager isn't limited to only PHP projects. There are many well known javascript libraries and even CSS frameworks who publish packages to composer. The real benefit is that once dependencies are required and installed with composer, from that point forward all the dependencies can be easily managed from the command line.

My specific use case is for a university — Florida Institute of Technology (www.fit.edu)

We have TONS of in-house and student projects to maintain. For example, our assets server has 100+ jquery plugins. Extremely time consuming to manually track all these down, check for new versions, upgrade, etc. Viewing what dependencies a project uses, what versions all of them are at and being able to easily update them is where composer comes into play.

I am not sure what you mean by it not being ready out of the box. I simply install with composer, then in my templates I reference the moxiecode/plupload/js/plupload.full.min.js and everything (at least what I am using with core API) just works.

Does that help clarify my use case?

[jayarjo]

Yes, that was pretty informative, thank you. Have you tried Bower?

[calmdev]

Yep, I was going to mention Bower — I figured you'd be familiar with that one! I use bower with all my node.js projects. I can understand your confusion with composer, because I had the same thoughts too initially. Given the nature of node.js we really only tend to see JS and some CSS packages there....no need for PHP or language XYZ packages.

In the PHP world it seems like nobody uses node.js tools like bower. Or maybe people just don't want yet another technology dependency - i am not sure. Composer can be distributed as a stand-a-lone PHAR (PHP Archive) which can be used like a typical cli tool so maybe people are just more comfortable with that.

FWIW, I do like bower more than composer. I originally did try using bower with the php projects, but found myself using composer for all the server-side PHP libraries. So instead of using two package managers I ultimately decided Composer for PHP and Bower for node.js

Anyways, nice talk and thanks for your work with PL Upload and TinyMCE. I 've been using them both for several years and they are great.