-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can Meteor package be upgraded to 1.2.3? #597
Comments
+1 It would also be awesome if you could fix the Atmosphere Github link to directly point to the repo for the Meteor package. I was trying to figure out if UI was already included, but can't tell since the Github link points to the core velocity Github repo. |
+1 |
Seems like it's been 20 days since you opened this issue and Julian still didn't update the Meteor package :( |
@danielkalen I'm the steward of this repo now. How does the meteor version work? I can get it pushed out soon if I know how to do it. |
I've typically only used bower and npm |
The links points to this? But now looking at the content of this repository it is already |
@mitar Here's proof that the current package located on atmospherejs is 1.2.1 http://share.danielkalen.com/2wM/ |
@kenwheeler You have to download meteor (obviously), and create a package possible using this tutorial: http://www.webtempest.com/meteor-js-packages-tutorial Basically you need to create the package dir and inside have a package.js (http://docs.meteor.com/#/full/packagejs) describing the behavior of the package, along with the latest version (I think minified) of velocity. |
Any updates on this? It has been a year since opened and we're still having access to Velocity 1.2.1 from Meteor packages. |
I've not had the time to look at it - beyond seeing that the tutorial link is dead - the atmospherejs link is saying 1.3.2 but I'm assuming it's grabbing the readme and not the js files? If someone wants to put together a Pull Request to add the needed things then it would be helpful :-) |
@Rycochet I'm not familiar with VelocityJS but thought I'd chime on on this and try to help as it was mentioned in a Meteor issue (linked above). As you said, the README is just getting updated from the GitHub README, but the package itself has been stagnant on 1.2.1 since it was initially released. Ultimately, I'm fairly sure this package isn't critical anymore as Meteor natively supports NPM modules. Though there do seem to be a decent number of legacy users using this Meteor package and Meteor packages are still actively maintained by many, so it's up to you if you want to proceed. I certainly think it can be deprecated in favor of the pure NPM version, but again I'm not familiar with this package. The process for creating a Meteor package is relatively simple and documented in this official guide: https://guide.meteor.com/writing-atmosphere-packages.html. You would need to install Meteor. It's not difficult, but perhaps a user who is more familiar with the process might more able to help you with it quickly... it appears that @chrismbeckett had originally published the package on Atmosphere, but I'm not sure if they're still involved. At first glance, it would appear that the Meteor package has never been checked into Git so you may be missing the package source for it which shows how it was laid out. I've gone ahead and attached it here in case it's helpful to anyone. In your case, the package is already created so you'll just want to bump the versions, reference the most recent versions of the JS and then run Anyhow, those are my two cents. :) |
Seems best to use the npm version since it's preferred now over Meteor packages. |
@abernix That's really useful, thanks :-) I'd like to get the Meteor package set to depreciated if possible then - so it uses the NPM package instead - will need to find out who controls the |
I think velocity is autopublished: MeteorCommunity/discussions#14 (comment) The issue is that since MDG discontinued meteor.com free hosting, autopublishing does not work anymore. |
It is still 1.2.1.
https://atmospherejs.com/velocityjs/velocityjs
The text was updated successfully, but these errors were encountered: