I'm trying to use the meteor 1.4 beta and wanted advice on the best way to get set-up - I've never used a software beta before and am a bit unsure.
Do I just download the latest file from github? In this case https://github.com/meteor/meteor/releases/tag/release%2FMETEOR%401.4-beta.7
How do I configure the file on my system such that I can use the meteor command in my terminal as normal?
Are there any other things I need to set up or be aware of to use this version?
Create a new project using the recommended (current) Meteor version :
meteor create test
Then upgrade the newly created project to the latest beta available :
cd test
meteor update --release 1.4-beta.7
There you go, the test project is on the latest beta and outside of it you can still use your system-wide Meteor install.
Regarding 1.4 specifically :
The latest dev bundle comes with MongoDB 3.2, if you're upgrading an existing project it will warn you about the need to migrate your database, the easiest way to do so in dev is simply to run meteor reset.
Also, meteor node still points to v0.10.45 but your app will run with v4.4.7 (just console.log(process.version)).
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.
So I updated to swift 3.0 and now my projects with realm 1.0.2 all give me an error.
RealmSwift compiled with older version of Swift language (2.0) than previous files (3.0)
I also tried to build a net new project and still get the build error, so I know it is not a conversion issue on the Swift side.
I found several Swift 3.0 beta users and tried to run the script to update my version to 3.0 and several other options. The last few posts appeared to use Cocoa Pods - which I don't currently use. Is that the supported fix path?
Any help or direction would be greatly appreciated.
I haven't tried it yet, but here is what should work.
Essentially, the compiler gives you a description of what went wrong. The framework was compiled with Swift 2.0, while your project or other files were compiled with Swift version 3.0 (which means you made the switch after upgrading to the new version of Xcode.
To fix this, you need to use the Realm framework compiled with a Swift 3.0 compiler. Since the Realm team doesn't yet provide a precompiled version compiled with Swift 3.0, you have to do so yourself. To do that, go to their Github repository, and follow the instructions in the README under "Building Realm":
Prerequisites:
Building Realm requires Xcode 7.3.
Building Realm documentation requires jazzy
Once you have all the necessary prerequisites, building
Realm.framework just takes a single command: sh build.sh build.
You'll need an internet connection the first time you build Realm to
download the core binary.
This should generate the Realm framework with the current compiler version, which you then just have to use to replace your current Realm framework with. After that, everything should compile as it used to.
As stated before, I don't know if this actually works, as I haven't tried it yet. I don't exactly know if Swift 3.0 is supported by Realm yet or if there are any other issues you could run into. So please let me know how this works out!
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'm trying to understand what the docs say about the meteor package server.
In addition to Isopacks, the Package Server contains distributions,
which are sets of packages that have been tested together by a release
engineer and that are known to work well together. For example, when
you use Meteor 1.0, you're using the METEOR distribution at release
1.0.
(https://www.meteor.com/services/package-server)
and
Other people can also publish their own distributions to the package
server as well. If developer alice published a distribution called
SPACE-ROCK, you could switch your project to it by typing something
like meteor update --release alice:SPACE-ROCK#1.2.
(https://www.meteor.com/projects)
I know I can browse packages thru meteor search ... or on atmosphere. But the distrubutions are not listed there.
Is there any way to search/list distributions published to the package server?
meteor search will show releases (I believe a 'distribution' is just a release), but from the documentation, I can't find any way to limit it to only show releases. Here's my result, as an example:
> meteor search
.... // literally all of the packages
Matching releases:
CORDOVA-PREVIEW An experimental release of meteor with Cordova support.
GITHUBBLE Release for githubble.meteor.com.
METEOR The Official Meteor Distribution
METEOR-CORE An experimental release of meteor.
WINDOWS-PREVIEW Preview of Meteor on Windows
diegosampaio:METEOR meteor 1.0.0 compatible
ekate:METEOR-SHOW Meteor Shows Things
ekate:REL-TEST test
ekate:TEST Packaging UX Wrangling
glasser:PUBLISHTEST Test release for isopack-cache branch.
glasser:TPS-PREVIEW Preview releases for tool performance and stability work.
glasser:UPDATE-TEST The official Meteor distribution.
konecty:METEOR meteor 1.0.0 compatible
lawshe:FULLPAGE Meteor smart package for FullPage.js. Create full screen pages fast and simple.
I tried replicating the todos application without using the example meteor terminal commentlets
Steps, i followed, (I'm using Ubuntu 12.04 build)
In terminal - meteor create todos
-- created the todos
a default *.html, *.css, *.js create underneath to the todos folder,
i deleted and replaced the actual todo artifacts into to it (e.g. client, server, public folders to the root) -> tried running the app - UI appears but the functionality breaks
I just wanna know what is ideal way create a app something similar structure as todos app.
This might help other folks to create a larger applications... currently i stuck in single *.js.
There's also a .meteor directory per project. Did you copy that too?
I've used a vagrant (https://github.com/pixelhandler/vagrant-dev-env) to install all of the dependencies and have an app running fine.
I just used 'meteor create myapp' like the docs say.
My bad i found it, just use this commentlet on terminal
meteor list --using
the above commentlet will list you out all the packages used for the current meteor project
Just add those project to the newly create meteor project and write your own structure, i found another way struture the project which i post as soon as possible...
meteor list --using
underscore
backbone
spiderable
accounts-ui
accounts-weibo
accounts-google
accounts-facebook
accounts-password
accounts-twitter
jquery
preserve-inputs
intersting fact is todo example comes two version one with secure and non secure packages - out-of-box build release with 0.4.2, and 0.5.0 respectively...