Three.js: Unable to get version newer than r77 from webjars

[OndrejSpanel]

Description of the problem

I am using Three.js in a Scala.js project. My preferred way to get Three.js is using webjars from SBT as follows:

jsDependencies += "org.webjars.bower" % "three.js" % "0.77.0" / "three.js" minified "three.min.js"

The most recent version I have found on webjars is r77, anything more recent does not work.

Three.js version

• r82

Browser

• N/A

OS

• Windows

[mrdoob]

I'm not sure there is much we can do about that...?

[OndrejSpanel]

I have zero experience with artifact publishing, therefore I do not know. A few questions which perhaps might lead in the right direction:

How does webjar publishing work? Who can place archives there? Were r77 and before revisions placed there by you, or someone else, someone unrelated?

[mrdoob]

I never heard of webjar before...

[OndrejSpanel]

OK. I will try to learn the ropes and check I can do something about this.

Current webjars release is https://bintray.com/webjars/maven/org.webjars.bower%3Athree.js

I have pushed "Add a new bower webjar", pointed to three.js github root, chose version r82 ... and voila ...

Deployed!
It will take a few hours for the Maven Central index to update but you should be able to start using the Bower WebJar now.
GroupID = org.webjars.bower
ArtifactID = three.js
Version = 0.82.0

I will check what automation options exist so that it is not necessary to do this manually for new releases. I have found a github project called WebJar for three.js, which was perhaps intended to handle webjar publishing (though it is currently release r68).

[looeee]

Three.js has stopped using bower though, so that might not work for versions after r83.

[OndrejSpanel]

Thanks for bringing that up. For reference: bower was removed in #10452. It should be possible use NPM packages for webjars instead for newer versions.

There already exist some NPM webjars for r72-r77 , but they seem broken to me, containing only package.json, README.md and shim.js files - see https://bintray.com/webjars/maven/org.webjars.npm%3Athree.js.

[OndrejSpanel]

I have tried to deploy r80 and r83 manually. Both show in their deploy log only this:

Generated POM
Converted dependencies to Maven
Resolved Licenses
Got NPM info
Determined Artifact Name: github-com-mrdoob-three-js
Starting Deploy

[mrdoob]

Issue solved then? 😊

[OndrejSpanel]

Not yet, I am afraid. r82 is deployed (bower), but newer revisions (npm) are not.

[mrdoob]

Uh? https://www.npmjs.com/package/three

[OndrejSpanel]

This is a NPM package, but not deployed as webjar, therefore not accessible through Maven / Ivy / SBT.

[mrdoob]

So, is there anything that we can do?

[OndrejSpanel]

I think I will be able to solve, but it will probably take a few days, as there are several things I have little experience with involved. If you do not mind this issue being open meanwhile, I will use it to track my progress.

[Mugen87]

@OndrejSpanel Any updates on this? Or can we close the issue?

[OndrejSpanel]

I am sorry, I was unable to proceed with this. For my purpose I have started including three.js by directly including the minified source.

[OndrejSpanel]

The issue no longer exists, most likely result of #10431 and commit d271add4e8e43f071e5d3cdbaef25ed3c2cd27d1.

I am able to download version 77-87 fine from Maven, the artifact page is https://mvnrepository.com/artifact/org.webjars.bower/three.js.