Mirror: A maybe slightly safer-ish wrapper around eval Function constructors

Update README

Changed files
+5 -4
+5 -4
README.md
··· 32 32 But really, I wrote this just for fun and I haven't written any tests yet and neither have I tested all edge cases. 33 33 The export being named `SafeFunction` is really just ambitious. 34 34 35 - However, if you found a way to break out of `SafeFunction` and did something to the outside JS environment, let me 36 - know and file an issue. I'm curious to see how far `evalish` would have to go to fully faux-isolate eval'ed code! 35 + [**However, if you found a way to break out of `SafeFunction` and did something to the outside JS environment, let me 36 + know and file an issue.**](https://github.com/kitten/evalish/issues/new) 37 + I'm curious to see how far `evalish` would have to go to fully faux-isolate eval'ed code! 37 38 38 39 ## Usage 39 40 40 41 First install `evalish` alongside `react`: 41 42 42 43 ```sh 43 - yarn add use-editable 44 + yarn add evalish 44 45 # or 45 - npm install --save use-editable 46 + npm install --save evalish 46 47 ``` 47 48 48 49 You'll then be able to import `SafeFunction` and pass it argument names and code,