Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible to use shim instead of forked hogan.js? #10

Open
morewry opened this issue Mar 13, 2013 · 2 comments
Open

Possible to use shim instead of forked hogan.js? #10

morewry opened this issue Mar 13, 2013 · 2 comments

Comments

@morewry
Copy link

morewry commented Mar 13, 2013

I've been wondering if it's possible to use a shim and the vanilla hogan.js file rather than the require-wrapped alternative version provided here.

Tried it and it doesn't work out of the box--is it possible? What would be needed to accomplish that?

@rafaelrinaldi
Copy link

Well, you can do it but unless you really need it, it's not worth the effort.
The nice thing of having a wrapped version of the plugin is that it makes use of features like pragmas (the plugin code is excluded from the output file generated by r.js) and module definition provided by RequireJS.

@tbranyen
Copy link

tbranyen commented Oct 6, 2013

@morewry what issue were you encountering? I'm looking over the plugin source and looks like it should work so long as your path is named hogan. Like:

require.config({
  paths: {
    "hogan": "path/to/your/hogan",
    "hgn": "path/to/requirejs-hogan-plugin/hgn"
  }
});

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants