-
Notifications
You must be signed in to change notification settings - Fork 24
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
Invalid top-level expression #29
Comments
thanks for this as I was going nuts trying to figure out what was wrong |
@karneaud , @FilmKnurd Were you using the default option? Because if you're not using that, metalsmith-layouts won't process anything unless it has the |
Ohhh...ok |
@karneaud So what was it, were you using the |
Sorry, There was a lot of issues I was dealing with at the time and admit I cannot remember how i solved it. I think it had to do with my files reference and the |
Then it shouldn't be a metalsmith-layouts related issue. It'll only process everything if the default option has been set. Otherwise only a |
I am hitting this issue as well. Can't seem to figure out how to avoid setting I would like to avoid that and rely on the default with a build file like this:https://gist.github.com/anonymous/379d3baaee3503050fdc however it errors out with:
|
Please move any discussion related to metalsmith-layouts to the metalsmith-layouts repo. Feel free to open an issue there. To answer your question @marr :
With your setup metalsmith-layouts will indeed only process files that have a layout set in the frontmatter. If you're going to use the I'll add a note in the readme for the use of the default key and hope that this solves it. If not feel free to open an issue: https://github.com/superwolff/metalsmith-layouts |
Thanks ismay, I will try the |
I'd use '*/.html', otherwise it won't match anything.
|
This is not a problem with this plugin, but I'm posting this in case someone else runs into this issue.
Compilation failed for me with
I thought the issue was with the SASS file or with this plugin. I finally looked at the plugin source code and saw that the data option was set to the file contents. It turns out all my files were being processed by the layouts plugin, so the data option had a bunch of HTML templating inside it. I just had to set the patterns option in the layouts plugin to only process markdown files.
This might be a good note to put in the documentation.
The text was updated successfully, but these errors were encountered: