I recently updated my meteor app to 0.6.5 and I noticed that the router package is not working properly, so I also did a mrt update, but there are still issues. For example, accessing routes does not render the appropriate template. When I run the router test there is also this issue:
Error: Cannot find module 'connect'
I noticed that there was an update to meteor router, but my app is failing to render the corresponding route-template.
Please let me know if there is a method to fix this issue. Thanks
Meteor Router has been updated to support 0.6.5. Note also that there will be the last (non bugfix) release and there is a new router project called Iron Router that will replace Meteor Router.
Meteor router doesn't yet support 0.6.5. It should do shortly as it just has to be slightly modified to work with the new version of meteor containing the linker branch. Why not consider the move to iron-router.
Tom Coleman (author of meteor-router) & Chris Mather worked to build it. It is compatible with 0.6.5
In the meantime, and more generally for mrt packages, you may need to downgrade to 0.6.4.1 until the package author has had a chance to update to the new package API that is part of 0.6.5. You can find instructions here - https://groups.google.com/d/topic/meteor-talk/BbrjGcGGIzc/discussion
Related
I added aldeed:autoform for my meteor project by including following packages.
aldeed:collection2
aldeed:autoform
After the inclusion, the routing of the application is crashed. For every route it says that the routes are not defined.
And after I remove the above aldeed:autoform packages from the project, the routing worked as expected. I want to know whether these two packages are incompatible or how to get the project working with these packages?
I'm fairly certain that IronRouter and Autoform are compatible with each other (it is a common combination). I'm wondering if you are having issues because of how you installed collection2. Per the latest Autoform README.md...
AutoForm 6.0 is now available and requires switching your app to using the SimpleSchema package from NPM and aldeed:collection2-core package.
I have not tested this but perhaps try following these instructions instead.
there should be more than 'no routes defined' error. any js error will break the routing. can you paste the whole console messages here?
I'm starting new app with meteor and I'm confuse when I have to install packages.
Meteor gives the possibility to install packages just like that:
meteor add <username>:<packagename>
Ok, very easy. The problem is that I would like use bower then, How I have to install the packages? For example angular.
meteor add urigo:angular
is the same as? what is the difference*? How I have to perform?
bower install angular
The logical conclusion could be use one of them, but I have seen in examples that they can be toguether.
*the package is recorded in different places, but the operation is the same?
With
meteor add <developer>:<packagename>
you add packages from the Meteor specific package database. Meteor packages are completely integrated into the Meteor eco-system and may contain both server and client side code.
You should use "meteor add" whenever possible.
To find Meteor packages you can use Atmosphere
Bower on the other hand is a framework independent package system for client side (mostly) JavaScript packages. It's not well integrated with Meteor - Although community packages exists to simplify usage of Bower packages with Meteor.
To answer you specific example:
meteor add urigo:angular
This command adds the Angular package of the Angular-Meteor project to your Meteor application. It's not only Angular but does also include some Angular services ($meteor) to provide integration of Meteor with Angular.
It even adds Angular support to the server side to some degree.
bower install angular
only downloads the official minified and non-minified javascript file of the latest Angular version for client side use.
You could use the Bower version with Angular but you wouldn't get the benefits of the integration.
While I don't use Bower myself, check out this package: https://atmospherejs.com/mquandalle/bower. I think it may help answer your question.
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.
Does anyone know where to find MeteorJS documentation for past versions? There does not seem to be an option on the website to switch to an older version like there is on other documentation sites.
You can download the tag for the version you want and run the app in the /docs directory.
The docs directory is a meteor app. All you need to do is meteor inside of it.
E.g for version 0.7.2:
git clone git#github.com:meteor/meteor.git
cd meteor
git checkout release/0.7.2
cd docs
meteor
open localhost:3000
One way is to dig in through the GitHub repo history for MeteorJS https://github.com/meteor/meteor/commits/devel/docs
Sorry to revive this thread a year in. But for users of the current Meteor 1.3 release it might be reassuring to know that you can get at least access to the Meteor 1.2 guide directly on guide.meteor.com via the small drop-down menu on top. Just switch it from "1.3" to "1.2".
For getting the full API docs or even older versions of the guide the currently accepted answer still applies, of course.
You can read it in plain text (with no sourcecode examples) at:
src meteor docs 0.6.5
src meteor docs 0.7.2
Since Meteor 0.6.0+ supports npm packages directly, is Meteorite still relevant, and would there be any advantage/disadvantage to using it?
Meteorite is definitely still relevant and recent talks from meteor team indicate it will be folded into meteor itself eventually.
Meteorite does more than NPM, it also takes client side 3rd party libraries and specifies how they get integrated into a meteor app. In this aspect it serves the same purpose as yeoman/bower. 3rd party client side libraries like x-editable, sugar.js, moment.js, etc dont really belong in NPM, but you also shouldnt have to manually incorporate them into your meteor project either. See this comment from the meteor team: https://github.com/meteor/meteor/pull/516#issuecomment-12919473
Meteorite doesnt provide the full functionality of NPM. With just meteor, you cant just require a NPM package in your app and use it, even in 0.6.0+ you still have to make a package and an api wrapper. If you wanted to use a certain NPM and it was already wrapped and shared on meteorite, that would in effect provide a NPM 'proxy' via a meteorite package. Like this package https://atmosphere.meteor.com/package/ncp
I would suggest using meteorite for the capabilities you gain beyond meteor itself. However, be aware that this is an area in great flux so you may have to rework/adjust your project in the near term. IMO if you are building more than simplistic apps, you'll definitely want meteorite for the ease of incorporating 3rd party libraries.
Meteorite is still relevant at this point. Even though NPM packages are supported in meteor there isn't a community repo to add packages from (http://atmosphere.meteor.com)
Even though NPM modules can now be added they still need to be made to work with meteor.
Meteor code uses fibers to allow sync code to run so each NPM module being used still needs a package to let it be used in meteor which can make it easier to use (by allowing fibers code to be used in a project) with minor editing. Currently these packages have no other community place to go besides the atmosphere repo.
Now you can have full access to NPM.
Just do meteor add meteorhacks:npm
See my article: Complete NPM Integration to Meteor