some compatibility notes about packages:
- packages now have their own namespaces (rather than needing to
use the global namespace). symbols you want to share should
be declared with an @export comment
- this also means that missing dependencies can hurt you. so don't
leave them out.
- your app's packages (in the 'packages' directory in your app) are
not automatically included in your app; you need to explicitly
run "meteor add" for them. this means that, eg, you can have test
helper packages which are not directly used in your app, but just
used by other packages' tests. (before releasing this, we may
make 'meteor update' fix current apps.)
- the bundle ("star") format has changed
- packages are now built into the "unipackage" format. if this format changes
before we release this code (and commit to the definition of the initial
versions of the formats) you may need to run "meteor rebuild-all"
- __meteor_bootstrap__ has been stripped of everything not related to
executing JS code. Some of what used to be there is now on the WebApp
object.
more detailed docs are likely to come before the 0.6.5 release.
What's left to do:
- "context" is now "computation"
- Autorun => Deps.run
- In Deps package, don't say "if we're inside a Deps.run" or anything else that assumes that's the only way to create a computation. Meteor creates computations for you for templates, etc.
- History.md update
- tweak docs
- refactor the "one per collection" check
- make errors into internal errors. Programming errors like returning the wrong
type from a function on the server don't need to be reported to the client.
