-
Notifications
You must be signed in to change notification settings - Fork 17
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
Nodent (and fast-async) break in Meteor #102
Comments
On another note, using |
For now, I can get by with There must be a better way to put things together for nodent-runtime without string source mangling at runtime? |
What's the best fast-async config for IE 11? From my limited knowledge, it seems like |
I don't have a planned fix for this right now. The If you want to submit a PR that fixes |
Thinking about this over the weekend, you could try replacing the first regex at https://github.com/MatAtBread/nodent-runtime/blob/master/runtime.js#L35 with TBH, I don't have the same setup as you, so I don't have a ready test-case to hand. However, if you pull (or fork) the nodent-runtime repo, |
I'll be getting back to this soon! |
I'm running code in Meteor, and I get
from the
processIncludes
function.This is because Meteor appends a commented line number to all source code, even from
node_modules
, so for examplebecomes
When
processIncludes
concatenates the lines of theinput
, the comments cause the remainder of the function to be commented out, for example:See here for more details: meteor/meteor#9160
The text was updated successfully, but these errors were encountered: