-
Notifications
You must be signed in to change notification settings - Fork 22
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
Lots of stuff #11
base: master
Are you sure you want to change the base?
Lots of stuff #11
Conversation
headless chrome on the fly)
added: injectPure, injectEffect
added: free variable detection in `extractDefinitions`
Could you move the browserify based unsafe eval into a separate module and then just require it at the top level there? I do not want to use it personally, but if it's usable enough, it would be better to have it in a separate module that can be imported on purpose. It would also be good to name it something sufficiently different from the unsafe string eval, since it goes through a large process. Even "evalViaBrowserify" or something would be fine in such a case. |
removed unused types
I discovered that that hack of mine still works as of 0.13.
Sorry for the awful state of the PR, just please tell me what parts of it do you agree to include, and I'll cherry-pick them.