Starting to think about how to support Meteor 3.0 and the changes that are going to need to happen in grapher. Some thoughts:

• I think we should skip intermediary support and jump right to the removal of fibers. You either use grapher with fibers or you don't.
• We need to support async filters and reducers. This should be easier since there will be a top level await.

There are currently 4 other community/third party packages used in grapher. It's worth exploring which ones of those will cause issues:

• matb33:collection-hooks - Keep an eye on it. Definitely needs updates. This is used on linker removal. If this isn't updated we can just recreate the after.remove hook and remove this package.
• reywood:publish-composite - Don't think we should have any problems with this one. I looked through it and didn't see anything that shouldn't be compatible with the removal of fibers.
• dburles:mongo-collection-instances - No issues.
• herteby:denormalize - Lots of collection hooks in this one. Also going to need some updates in it to make it async.

I'm waiting for the 2.8 release to get started on this but let me know if you have any other thoughts.