-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
error: handlebars does not support render #31
Comments
related assemble/assemble.io#158 |
@eurolife are you using something like |
Please bear with me, as I am quite new to this, but in my grunt file, there is grunt.registerTask and after that grunt.task.run which runs the specified tasks. There is also grunt.initConfig which defines all the tasks beforehand. Does that help or are you looking for something else? |
It's okay, I remember going through the same thing like it was yesterday lol. There is a lot to take in...
Could you add your entire gruntfile to a gist? https://gist.github.com/. If so that would be great, then just link it back here. If not, that's ok we can try to step through it |
Here is a link to it https://gist.github.com/eurolife/8062a7170e9efe937798 |
Hmm, nothings jumps out at me. just thinking out loud so we can try to narrow the problem down:
i'll keep looking too |
oh, I almost missed this. You mentioned that you're using
let me know if that helps |
Ok, I did what you said - I removed node_modules and also removed assemble from package.json and then installed grunt-assemble. After that I also had to do npm install otherwise grunt serve would not run. Unfortunately, I am still getting that same error after doing all of that. |
fyi i did try running assemble by itself and got the same error. |
do you have any custom helpers? or are there any helpers that are included by the generator? |
@eurolife can you link to an entire repository or at least create a gist with the package.json? Also, will you post information your environment like OS, node and npm versions? |
Do you mean helpers in handlebars? I didn't add any and don't know if the
|
I'm out the door now but will put my project up on github later and will
|
I just figured it out. In Since It works if you add a In later newer versions of |
indeed. great debugging @doowb! |
btw, should this be reported as a bug to handy, or |
Looks like @johnyb already tracked this down: helpers/handlebars-helpers#199 He's opened issues on both |
Unfortunately, both projects seem to be dead. 💀 :\ At the moment, I'm working around this using an npm-shrinkwrap.json file and artificially place the dependencies in a way, everything works as before npm@3. |
that's right I remember now, thanks @johnyb. seems like we should be able to do patches to fix this. |
That worked! Thank you so much! |
I encountered this issue by appending Changing Not sure if it's the same for every instance of this error, but hopefully someone else can save some time. For reference, here are my dependencies which are working:
|
@yan-kisen YOU ARE RIGHT! It's not an option for us to change this but maybe I can look at a fix for this /cc @masterbee |
We've just encountered this error now. Our project, including the gruntfile is here: https://github.com/standrewsdigital/digital-pattern-library Similar to yan-kisen, above, we get the error "Warning: handlebars does not support render." if we append a pre-release tag on the end of the version number. The package.json documentation says "Version must be parseable by node-semver, which is bundled with npm as a dependency. " If our version number is "version": "0.9.0" then the build works, but if I add a pre-release tag, e.g. "version": "0.9.0-alpha.1" then the build fails. Our devDependencies list: "devDependencies": { UPDATE: I have resolved this by navigating to |
I had the same problem. Turns out, the top-level project did not have any "version" field in the package.json file. Adding this field fixes the issue. Is is not sufficient for the field to exist, but it has actually contain a proper semver value. The specs for package.json actually request this field and the correct formatting, so the best fix for this issue would be to add a check in grunt-assemble and improve the error message. Thanks to garethjmsaunders for your hint! |
I had the same problem. It seems that the cause was that I put a version like the following in my {
"version": "1.0.0-rc.1",
} When i changed to |
@jonschlinkert @doowb I was able to create a fix for this by extarcting the single method used in the |
Thanks @yan-kisen, removing -SNAPSHOT in the version fixed my problem :-) |
@elpeq if you update to the latest version, you don't need to remove your -snapshot anymore. |
If you're experiencing this issue. please add information about your build to this issue (please, don't create another issue)
The text was updated successfully, but these errors were encountered: