Package.register_extension API.
It didn't even actually work for producing JavaScript files (eg a
coffeescript-like package): see #1410. Package maintainers should have upgraded
to the more powerful 0.6.5 API by now anyway.
- Fix order of ')' and '.' in a bunch of places
- Remove last reference to "smart packages"
- Fix an Atmosphere link
- Linkify a bunch of other things (CoffeeScript, npm, GitHub bug tracker, etc)
- Added a newline after the dot in "`meteor`. `meteor`". It looked way more
like `meteor.meteor` when rendered.
- Name `api.add_files` explicitly.
- Fix capitalization of GitHub
- Explain how weak deps check if the dep is there
- A few other typos
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.
This definitely won't "work" because both have API changes.
UglifyJS 1 was having issues minifying certain code (eg lodash). But UglifyJS 2
was occasionally segfaulting (as was other code using large regexps). See the
bottom of https://github.com/laverdet/node-fibers/issues/89
Hopefully this will fix it.
Instead of a general client-side sub de-duping mechanism (which mostly existed
for the sake of autosubscribe, and causes issues with server-driven
unsubscribes), make Meteor.subscribe explicitly aware of reactivity.
Expose an "invalidated" flag on Meteor.deps.Context.
Guarantee that invalidation callbacks from different contexts will not be
interleaved at flush time. This has the implication that if you do
context1.onInvalidate(function () {
context2.invalidate();
});
and this is the only way to invalidate context2, then context2's invalidation
callbacks will not be called until after *ALL* of context1's callbacks are
called. This allows us to be sure that the "unsubscribe, unless autorun tried to
re-create an identical sub" logic runs after the autorun function is rerun.
