Question 1

How do I replace a template in Meteor without losing its original events?

Accepted Answer

Use the replaces() method from template-extension: define a new template and call Template.newTemplate.replaces('oldTemplate'). This swaps the render function but keeps the old template's helpers and events intact, as shown in the README's foo2 example.

Question 2

What's the difference between inheritsHelpersFrom and replaces in template-extension?

Accepted Answer

inheritsHelpersFrom only copies helpers from another template, while replaces completely overrides the template's rendering but preserves the original's helpers and events. replaces is for full replacement, whereas inheritance methods allow partial reuse without changing the template name.

Question 3

Is aldeed:template-extension compatible with Meteor 2.0 or newer?

Accepted Answer

The README specifies compatibility up to Meteor 1.2+ for 4.x.x releases, but it doesn't explicitly mention Meteor 2.0. You should check the GitHub repo or package updates for newer Meteor versions, as it might require adjustments or forks.

Question 4

How does template.parent() work with block helpers in Meteor?

Accepted Answer

The template.parent() method accepts an includeBlockHelpers parameter; by default, it skips block helper instances, but setting it to true includes them in traversal. This allows fine-grained control over parent access in complex template hierarchies.

Question 5

Can I use template-extension to add hooks to all templates for debugging?

Accepted Answer

Yes, Template.onCreated/Rendered/Destroyed lets you attach global hooks to every template. For example, you can log all template creations for debugging purposes, as demonstrated in the README with console outputs.

Question 6

Template-extension vs manual template overriding: which is better for Meteor?

Accepted Answer

Template-extension simplifies manual overriding by providing built-in methods like replaces() and inheritance, reducing boilerplate and error risk. However, for very simple cases, manual overrides might suffice without adding a dependency.

Question 7

How to clear event maps for a template in Meteor with template-extension?

Accepted Answer

Call Template.templateName.clearEventMaps() to remove all event handlers added to that template. This is useful when inheriting events and needing to reset them, but note it clears all events, not selective ones.

aldeed:template-extension

What is aldeed:template-extension?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions