My meteor current version is 0.9.4, and I want to try the latest version "1.0-rc11", I've tried meteor update —release 1.0-rc11 and meteor update —release 1.0-rc.11, and I always got this message "Your packages are at their latest compatible versions."
You have packages that are not compatible with the rc.
Meteor 1.0 is out. You may want to try that with meteor update.
Have a look at what the packages you have are and their constraints to find out whether they are compatible with 1.0. If you have older packages it might prevent an update until you sort them out.
You can check the packages you have in your app using meteor list
Related
Just trying to update Meteor CLI from version 1.12 to 1.12.1 but in general, what's the best way to update Meteor's CLI?
To specifically update the Meteor CLI, without having to update a meteor project as well, you can move into any folder that is not a Meteor project folder and run the meteor update command
There are several kinds of update:
downloading the newest Meteor tool
updating the current project to the latest Meteor tool version (implies 1.)
updating all packages to their latest versions
You can all manage that by using the meteor update command with (or without) the respective flags, like --patch, --packages-only or --all-packages.
See: https://docs.meteor.com/commandline.html#meteorupdate
You can also type meteor update --help for information on the respective flags.
Definitely no need to re-install the tool. Running meteor update outside of the meteor project does update just the command line, but you should be really updating your project by running meteor update --release <version> in your project folder.
The latest version of an Atmosphere (meteor) package has a serious bug, so I want to indicate an old version number for it. But I can't find a version list of it on its Github page nor on the Atmosphere page.
Is there a way to list up all version numbers of an Atmosphere (meteor) package?
You can use the meteor show command, spcifically with the --show-all flag like this:
meteor show --show-all package:name
This question already has answers here:
how do I install a previous version of meteor JS?
(5 answers)
Closed 4 years ago.
I recently updated my Meteor version from 1.6 to 1.7, which seems to have unexpected bugs. In an attempt to fix them I reinstalled Meteor, which probably deleted old installations, which means I can't go back to 1.6. If I change the version in the .meteor/release file from 1.7 to 1.6.1.2, it says that I need to update the release to 1.7, which means I can't use the old version anymore. Is there any way I can install 1.6 version?
I'm using Windows 10 PC.
Are you tracking your project in version control?
The usual advice here is that you should make sure your app is committed to some VCS before starting the update so you can roll back. This works because Meteor uses the versions in .meteor/release and .meteor/versions to keep track of what to use to run your app.
Rolling back
In the unlikely event that the update leaves your application in a bad state, and you don’t feel like debugging it right away, please make sure your application’s .meteor directory is committed to your version control system (e.g. Git, Mercurial, etc.) before the update, so that it’s easy to revert the changes if you encounter problems.
If you don't have any version control, then my recommendation would be to update .meteor/release as you have tried, and also delete .meteor/versions and allow Meteor to pick versions again that are compatible with 1.6.1.2
Alternatively you could try creating a new project with Meteor 1.6.1.2, add the same package dependencies and copy over the release and versions files for the same set of packages.
$ meteor create 1612 --release=1.6.1.2
$ meteor add <packages from your app>
After you've copied them over, meteor should use version 1.6.1.2 and compatible dependency versions
In my Meteor project it looks like I've got two versions of jQuery running. My app is using the atmosphere package materialize:materialize and I know that one of its dependencies is jQuery. In my meteor/packages folder it shows version 1.11.10 being used.
But the confusing part is in my External Libraries folder. It also shows a version of jQuery 2.0.0. The only npm package that I have used for my app was when I brought in the babel runtime that was required for Meteor version 1.4.3.2. I had in the past installed Materialize from npm but removed it some time ago. Confused to why that jQuery 2 is there.
This is fine, it happens this way because of package dependencies, Meteor depends on what is quite an old version of JQuery, and one of your npm packages depends on 2.0.
It does seem strange, but it isn't a problem.
What is happening here is some of the meteor packages depends on jquery and some of the npm packages does the same so you end up having the lib installed twice. Nothing terrible except that clients would have to download the same library twice. This is a known bug here https://github.com/meteor/meteor/issues/6626. Not sure where is it going though, it's been there for quite long already.
I am trying to run a project on meteor but getting this error in the command line-
this project uses Meteor1.0.2.1, which isn't available on Windows. To
work with is app on all supported platforms, use ,meteor update
--release METEOR#1.1.0.2 to pin this app to the newest Windows-compatible release.
I have tried updating to which I am getting the error message
while checking for meteorhacks:kadira-binary-deps#1.2.1:error: No
compatible binary build found for this package. Contact the package
author and ask them to publish it for your platform.
I tried updating this to which i was brought back to the first error message.
Does anyone know how I can run this meteor package? It is sparrow-finance to be specific.
Regards
Chris
The answer is simply remove the kadira package which you can do by editing the packages file in .meteor.
But, kadira is really useful. So what I'd suggest is to set up meteor environments. Meteor cookbook has a good example of this - https://github.com/awatson1978/meteor-cookbook/blob/master/cookbook/environment-detection.md .
If your environment is anything other than local, use kadira, else don't use it.