we are developing our meteor application in a windows environment using the unsupported windows version of meteor. The latest release is 0.8.3. Ok in the windows environment we used meteor add for the packages. But if i write
meteor add meteorhacks:kadira
meteor add kadira
I always get the no such package message. mrt command doesnt work. Any ideas?Thanks
I think this question is duplicated. Please refer here
meteor add meteorhacks:kadira is available only in Meteor 0.9 and above.
For Meteor below 0.9 you have to use Meteorite which is currently not supported by windows.
I'm developing an application in Meteor 0.8.3 and I have to use mrt: https://github.com/oortcloud/meteorite
The command is:mrt add kadira
I highly recommend you to upgrade as soon as possible. If you application depends on atmosphere packages, you'll have a hard time try to upgrade it later. Today most packages are obsolete because the creators don't care about it anymore.
Having in consideration that you're using an unsupported windows version: I don't really know if this is going to work. It's work great for Meteor at version 0.8.3 today.
Related
It seems that the only way to upgrade the version of Node used by Meteor is to upgrade Meteor, according to the following:
How to change or upgrade the version of Node.js in Meteor
Update Node version for Meteor app deployed to Heroku
You can run your production bundle with other node versions, it is just not guaranteed that it will work. In practice though, I've done this many times and have never run into any issues (always using newer versions of node).
In development meteor uses the node binary in
~/.meteor/packages/meteor-tool/METEOR_VERSION/mt-os.linux.x86_64/dev_bundle/bin/
where METEOR_VERSION is the version of meteor your project is using, e.g., 1.12.1. So you could go there and replace that binary with a symlink to another node executable if you want to and it will probably work for most newer versions of node.
In development: difficult. Your Meteor project uses its own embedded Node version, and trying to change it might also require reconfiguring the dev mode build and tooling...
In production: if you have control of the server environment, then yes, you can try another Node version, at your own risks regarding compatibility with Meteor code. However the latter checks that your Node major version is at least the one required by Meteor.
In Heroku: if you use the Meteor buildpack horse, then no. The buildpack configures your Heroku environment as required by the Meteor version of your project, including the Node version.
I was trying to upgrade my RN from 0.19 to 0.27 using the commands from the doc,
i.e.
npm install --save react-native#0.27
react-native upgrade (I chose the overwrite option when asked to update the latest RN files)
The npm install step worked fine but the upgrade step wiped out all my code in android plugin folders and any changes made to MainActivity.java. My environment is : MacOS, Genymotion, Android development
Thanks!
You've missed that react-native upgrade asked you if you want to overwrite your files. react-native upgrade replaces your files with newer version if it's different than the default one. It does not merge your changes. Also jump from 0.19 to 0.27 is a big one so probably there was a lot of changes.
Yes, react-native upgrade will wipe everything out. There's a command line option now (react-native link) that will put most of it back in, but not everything.
If you choose not to overwrite the files you are risking not including something very important and it may break the upgrade.
I don't know of a good way around this. My process is to use a good ide that shows me exactly what has changed between upgrades. Then I go though each change and see if I'm missing something. The java code and android studio files tend to be quite easy. But the xCode stuff is not, the pbxproj file is particularly awkward. You mostly need to reconstruct it by using Xcode. So... every time you do something to the xCode project, make a note of it! Yes this is a terrible solution, but I don't know what else to do.
I've ended up making detailed notes about everything I do during an upgrade. And I upgrade recently because its easy to forget.
I'm taking an Eduonix tutorial about meteor and I'm using joshowens, but it sends me this error while I'm trying to add the package:
"joshowens:accounts-entry INCOMPATIBLE WITH METEOR 0.9 OR LATER".
And as long as I'm working on windows it doesn't allow me to downgrade my Meteor version, could you help me?
For Meteor 1.2.0.1 version the following should work:
meteor add check
meteor add selaias:accounts-entry
Does anybody know if this issue of old node versions regarding using https://github.com/dockyard/es6_module_transpiler-rails on Heroku has been resolved.
https://gist.github.com/bcardarella/7384208
Copying the gist:
I have been working with Peter Wagenet from Tilde on getting support
for Ember Appkit on Heroku with a Rails app. First some background:
Ember Appkit will Transpile ES6 modules for use as AMDs. To that end I
wrote the es6_module_transpiler-rails gem which uses Node and Square's
es6-module-transpiler package. That package makes use of Esprima for
the parsing. There is an issue of a reserved keyword in older
JavaScript runtimes not being quoted properly:
https://code.google.com/p/esprima/issues/detail?id=469
On our local machines everything works OK and the transpiling does not
bomb out because our versions of Node are recent. However, when we
deploy to Heroku and Rails attempts to pre-compile its assets the
version of Node that Heroku uses is out of date. Based upon some
research it appears by default Heroku is using Node v0.4.7 which is
from April 2011. It is easy enough to force Heroku to use a more up to
date version of Node:
https://devcenter.heroku.com/articles/nodejs-support#versions however
it is currently unclear if this will run side-by-side with a Rails app
for pre-compilation. Furthermore, I do not think it is reasonable to
ask Rails developers to include Node configuration code for Heroku in
the apps.
I respectfully request that the default version of Node for Rails's
asset compilation get bumped up to a more recent version.
we support integration through node by using multi buildpack and by defining a package.json in your application. Here's the PR https://github.com/heroku/heroku-buildpack-ruby/pull/245
Make sure nodejs comes first in the .buildpacks file then you can get any version of Node you want.
I wonder if all Heroku addons - that are currently working for Rails - will work for Node.js once the support is there?
And what is the ETA for the launch of Node.js support?
Node.js is now officially supported on Heroku.
Several addons currently require specific ruby gems to be installed so I think Node.js will have its own separate set of addons.
As for launch, to my knowledge there is no ETA yet.
Whether or not an addon will work with node is going to specific to the addon itself, probably whether the addon requires a Ruby lib to work.
I'm currently using Loggly, RedisToGo, Mongolab, and RabbitMQ via Addons all with node.
It is supported by CEDAR stack on heroku
All you have to do is put into .gitignore node_modules directory and create Procfile eg.
web: node web.js
This is just a command to startup your application.
Important thing is that you should layout your app as node_module i wrote a blog post about it
http://no-fucking-idea.com/blog/2012/04/23/building-node-dot-js-module-using-npm/
So you can look it up.
url explaining how to deploy is here:
https://devcenter.heroku.com/articles/nodejs
Have fun!