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

Uncaught TypError: Cannot call method 'merge' of undefined #545

Closed
astrotars opened this issue May 31, 2013 · 8 comments
Closed

Uncaught TypError: Cannot call method 'merge' of undefined #545

astrotars opened this issue May 31, 2013 · 8 comments

Comments

@astrotars
Copy link

Throwing error in compiled templates. Using v1.0.12. Revereted to v1.0.11 and everything is back up and working.

@kpdecker
Copy link
Collaborator

What version of the client runtime are you using?

@astrotars
Copy link
Author

1.0.0-rc.4, the latest available from cdnjs.com.

@kpdecker
Copy link
Collaborator

You need to use 1.0.0 final which has an open PR here. I'm not sure when this will land but hopefully soon.

Closing this for now but please let me know if you run into issues with the updated binary.

@tiye
Copy link

tiye commented Jun 5, 2013

I encountered this issue after I ran sudo npm update -g handlebars updating handlebars to 1.0.12.
Also the exception disappeared as I switched back to 1.0.11.
The latest package on NPM remains 1.0.12. What's its relationship with 1.0.0-rc4?

@kpdecker
Copy link
Collaborator

kpdecker commented Jun 5, 2013

https://github.com/wycats/handlebars.js/blob/master/release-notes.md shows the matching node and client versions.
1.0.12 is equivalent to the 1.0.0 client release.

Starting with the next release we are going to unify the versioning as we can move to 1.1.* versions.

On a side node I just had confirmation that the 1.0.0 pull request to cdnjs was merged so presumably this is available or will be available soon.

@tiye
Copy link

tiye commented Jun 5, 2013

Got it. I'll just keep using v1.0.11 until v1.1.* published.

@kpdecker
Copy link
Collaborator

kpdecker commented Jun 5, 2013

I would recommend v1.0.12 + the 1.0.0 client but if you can't change that
for whatever reason then that should work.

On Wed, Jun 5, 2013 at 9:31 AM, jiyinyiyong notifications@github.comwrote:

Got it. I'll just keep using v1.0.11 until v1.1.* published.


Reply to this email directly or view it on GitHubhttps://github.com//issues/545#issuecomment-18979730
.

@tiye
Copy link

tiye commented Jul 31, 2013

My problems Soleved

Just add some details here in case someone is misleaded by my previous posts.

After looking into #547 I found that even the pre-compiled code requires a handlebars.runtime.js to work in browser. So update that script and it would be OK to use Handlebars 1.0.12. That script could be downloaded from a link on the home page.
The whole project is not started by me, and I thought the scripts are already wrapped in the pre-compiled one. And that was wrong in this case.

And the Grunt plugin talked about this problem too.
gruntjs/grunt-contrib-handlebars#55

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