You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started down the road of correcting the in-node implementation, but we are going to have to statically analyze the template string during the transform somehow. I'm not too familiar with this kind of thing. Any ideas?
i wrote my thoughts on sheetify static evaluation in #54 (comment). meanwhile support for template strings has been merged into static-eval: browserify/static-eval#13. 🍍
@yoshuawuyts you sure this works? you'd have to gather up and pass in all currently defined variables to static-eval, i thought you said you'd rather avoid the complexity.
@yoshuawuytshttps://github.com/yoshuawuyts you sure this works? you'd
have to gather up and pass in all currently defined variables to
static-eval, i thought you said you'd rather avoid the complexity.
—
You are receiving this because you were mentioned.
This is because dynamic code can't be interpreted during compilation. You
can, however, export dynamic code that we can later import from a `.js`
file. See
5817cb0
Thanks for the response ,but i don't sure if this solution work for my use case:
I want to update position of an element with the last coords of mouse pointer.
I don't know values of my css property in advance.
Activity
ahdinosaur commentedon Oct 2, 2016
i wrote my thoughts on sheetify static evaluation in #54 (comment). meanwhile support for template strings has been merged into
static-eval: browserify/static-eval#13. 🍍yoshuawuyts commentedon Nov 16, 2016
Should be fixed in
6.0.1which has the lateststatic-eval- holler if something's not working as expectedahdinosaur commentedon Nov 17, 2016
@yoshuawuyts you sure this works? you'd have to gather up and pass in all currently defined variables to
static-eval, i thought you said you'd rather avoid the complexity.yoshuawuyts commentedon Nov 18, 2016
Oh, didn't realize that's how it worked - nah this doesn't work then
On Fri, Nov 18, 2016 at 12:53 AM Mikey notifications@github.com wrote:
sepiropht commentedon Sep 25, 2017
i'm using the last version, and it still not fixed
yoshuawuyts commentedon Sep 25, 2017
sepiropht commentedon Sep 25, 2017
Thanks for the response ,but i don't sure if this solution work for my use case:
I want to update position of an element with the last coords of mouse pointer.
I don't know values of my css property in advance.