Closed stevenvachon closed 10 years ago
hmm, hard to tell. i'd be curious to know what console.log(myth(styles))
returns
It doesn't log anything because of the error.
hopefully fixed in 1.0.0
, let me know if not
Still not working.
The comment in this block is what throws the error:
@keyframes section-intro-children
{
0% { opacity:0 }
25% { opacity:0 } /* simulates a delay */
100% { opacity:1 }
}
With the comment removed, it parses without error.
It's not the same issue at all. Reported here https://github.com/reworkcss/rework-vars/issues/32
Fixed here https://github.com/reworkcss/rework-vars/pull/33 Hopefully released soon (as a rework-vars update, so you will just need to delete & reinstall myth, or run npm update myth (not sure if this last one works, I never understand what npm update does ^^))
Thanks!
The issue came from the rework-visit helper, I'll try to fix than asap.
Logging out
styles
gives me accurate CSS, and simply doingreturn styles
works fine. Am I missing something somewhere?Here is the full error: