Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
syntax error, unexpected modifier_if
See original GitHub issueError
Getting error /gems/sass-3.5.1/lib/sass/script/functions.rb:2050: syntax error, unexpected modifier_if (SyntaxError) when trying to start a rails server.
Release Version
3.5.1
Code
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Why do I need extra parentheses for conditional modifier?
[1 if true] # SyntaxError: unexpected modifier_if, expecting ']' # [1 ... parentheses you have no an error because it return nil or...
Read more >[Script] Syntax error : Unexpected token ) | Roll20
Hi ! I try to add this script ("new script" button) to my campaign, but I get this error (in API Output Console)...
Read more >How to Fix the "Parse Error: Syntax Error Unexpected" In ...
The parse error syntax error unexpected may intimidate you and is completely understandable, but, debugging errors is not too complicated.
Read more >[RESOLVED] Please help... Parse error: syntax error, unexpected ...
Hello everyone! I am new to PHP and I am trying to build a login for a club website at our school. This...
Read more >Ruby | Keywords - GeeksforGeeks
source_file.rb:14: syntax error, unexpected keyword_end, expecting end-of-input ... if, Used for if and modifier if expressions.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Possibly related to this ruby bug: https://bugs.ruby-lang.org/issues/10279 ?
Reverting to release version 3.4.21 resolved the errors.