Retain compilation runtime when registering precompiled partials

[Schommer79]

I am trying to write template modules, where a javascript module exports a template function. Ideally, each template module would be isolated so as to neither affect, nor be affected by the other handlebars runtimes (handlebars.noConflict().create()). Different templates could depend on different versions of a helper with the same name without stepping on each other. Each template module should also handle registering any helpers/partials it needs.

For simple templates, this can be done with no modification to how handlebars currently works. However, if a template requires a partial, and that partial requires other resources such as a helper, it stops working. I compile the partial template in its own runtime, with needed helpers already registered to that runtime. But when that partial template is registered in a second runtime, templates created in that runtime fail when they try to use the partial due to missing helpers.

I suspect that the runtime of the template being executed overwrites the runtime of the compiled partial and that is why it fails with helper not found.

Is it possible that partials could be tweaked to retain their compilation runtime? Or that an option could be added to allow that to happen?

[jaylinski]

Please create an example of your setup. I'm not quite sure if I understand the issue correctly.

[Schommer79]

If we have one file (partial.js):

import handlebars from "handlebars";

const hbs = handlebars.noConflict().create();

hbs.registerHelper("foo", function (value) {
    return "foo was called with: " + value;
});

export default hbs.compile("hello from partial, {{foo name}}");

and another file (template.js):

import handlebars from "handlebars";
import partial from "./partial.js";

const hbs = handlebars.noConflict().create();

hbs.registerPartial("part", partial);

export default hbs.compile("hello from template, {{> part this}}");

If I were to then import template.js and call it with {name: "John Doe"}, I would want the following result:
"hello from template, hello from partial, foo was called with: John Doe"

Instead, it throws an error that there is no helper called "foo"

[Schommer79]

An example of the isolation aspect:

If I had another file (template2.js):

import handlebars from "handlebars";
import partial from "./partial.js";

const hbs = handlebars.noConflict().create();

hbs.registerHelper("foo", function (value) {
    return "I am a different foo helper, called with: " + value;
});
hbs.registerPartial("part", partial);

export default hbs.compile("hello from template2, {{foo name}}, {{> part this}}");

If I were to then import template2.js and call it with {name: "John Doe"}, I would want the following result:
"hello from template2, I am a different foo helper, called with: John Doe, hello from partial, foo was called with: John Doe"