Home > Error Invalid > Error Invalid Top-level Expression

Error Invalid Top-level Expression

Terms Privacy Security Status Help You can't perform that action at this time. You signed in with another tab or window. anlutro referenced this issue in sass/sass-spec Mar 16, 2015 Merged Spec for libsass issue 941 #277 xzyfer added bug test written labels Mar 16, 2015 xzyfer commented Mar 16, 2015 Spec Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. http://qtechnology.net/error-invalid/error-invalid-asset.html

Thanks you for that great tool. How to compose flowering plants? Fired because your skills are too far above your coworkers How can I get bash/zsh to change some text from "foo.foo.foo" to "foo foo foo" with a script/alias? MadRabbit closed this Dec 8, 2012 MadRabbit reopened this Dec 8, 2012 Sass member andrew commented Dec 9, 2012 libsass, the C library that node-sass is built on only has support

When I'm trying to compile just anything simple lie body background: pink I'm getting this error ERROR -- , line 1: invalid top-level expression Maybe i'm doing something wrong? Comment every line of code? Do 40% of U.S. I finally looked at the plugin source code and saw that the data option was set to the file contents.

  1. Why do Internet forums tend to prohibit responding to inactive threads? "Non possunt dari" translation Efficient Typing on a Gameboy FizzBuzz Implementation in Java What is the maximum interception angle for
  2. Fixes sass#941 8dd7ecc mgreter referenced this issue Mar 17, 2015 Merged Refactor parser for css block comments #955 mgreter closed this in #955 Mar 19, 2015 This was referenced
  3. Rowno commented Jan 10, 2015 👍, errLogToConsole: true should output a filename for top level source file errors.
  4. I guess since my layout is .html, I would set the pattern to just '.html'.
  5. Make sure you're not mixing them up!
  6. It had a line number at the end.
  7. If I change the gulp.src to anything other than what it's currently set (the existing correct directory) the error will go away. –Joel Z.
  8. I'll investigate and report if I find anything of use to libsass.
  9. Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc.
  10. Skip to content Ignore Learn more Please note that GitHub no longer supports old versions of Firefox.

Already have an account? You signed in with another tab or window. Already have an account? What is the command to remove all files but no folders?

We recommend upgrading to the latest Safari, Google Chrome, or Firefox. juanpasolano commented Jul 25, 2014 Thanks... I can confirm this is still an issue. It's the extension name that caused the problem.

How to increase the height of a single row in table? Changelog [New] Linux Versions [Improvement] New asar format starts up Prepros 2X fast [Improvement] Offline Installer [Improvement] Faster compile times with totally rewritten new compilers. [Change] Browser Sync is disabled by Already have an account? I think it had to do with my files reference and the metalsmith-ignore.

Reload to refresh your session. I'll add a note in the readme for the use of the default key and hope that this solves it. See error list for details \Web\Content\scss\/tool-comp/_variables.scss:103: error: invalid top-level expression */ Also posted in WebEssentias git and said that must be a libsass bug. Should I have doubts if the organizers of a workshop ask me to sign a behavior agreement upfront?

we can probably provide a plugin to implement something I already proposed in sass/sass-spec#136 (comment). this contact form Terms Privacy Security Status Help You can't perform that action at this time. You signed out in another tab or window. That way we could include tests for sourcemaps and errors/warnings (and other more API consumer specific issues).

lcb931023 referenced this issue in vigetlabs/gulp-starter Mar 12, 2015 Closed Not watching Sass files in sub-directories under src/sass/ #101 Snugug added this to the 2.0.0 milestone Mar 31, 2015 Snugug added Reload to refresh your session. I just had to set the patterns option in the layouts plugin to only process markdown files. http://qtechnology.net/error-invalid/error-invalid-timestamp-0-last-0.html Please pay close attention to the new sass-spec issue format i.e.

ismay commented Nov 23, 2015 I'd use '**/*.html', otherwise it won't match anything. … On 23 Nov 2015, at 19:16, David Marr ***@***.***> wrote: Thanks ismay, I will try the pattern more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Because if you're not using that, metalsmith-layouts won't process anything unless it has the layout key in the file's frontmatter.

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.

Otherwise only a layouts key will trigger it. nene commented Oct 14, 2014 I too ran into this error. You signed in with another tab or window. But the compiler Mindscape Web Workbench does not have problems compiling it.

will pass the spec for this issue. You signed out in another tab or window. Maybe that is the problem?? http://qtechnology.net/error-invalid/error-invalid-arm-agent-name.html Comments are built with // not #.

I guess we should promote the following command set in the future: sass --unix-newlines --sourcemap=none -t nested -C "input.scss" "expected_output.css" sass --unix-newlines --sourcemap=none -t compact -C "input.scss" "expected.compact.css" sass --unix-newlines --sourcemap=none From the error and your explanation above, I'd think it was still a -sass issue, since the error is coming from metalsmith-sass and prints "Invalid CSS". kevinSuttle commented Feb 5, 2014 I'm going to close this for now, as I have it running on another project and fine. sass-spec init --issue 123 mgreter commented Mar 14, 2015 As @am11, myself and others already have put it, we should probaly create a dedicated spec runner inside libsass repo (in C/C++).

You haven't provided your SASS file so I have to guess, but from what you've said it's probably the same cause. @mastertinner's answer has the solution. –Modus Operandi Feb 21 '15