Avoid eval for Rollup.js
See original GitHub issueHi guys, I’m currently using the branch-sdk with rollup.js but I get the following error:
rollup: Use of
eval
(in /home/gp2mv3/www/covevent/refonte2/ionic/node_modules/branch-sdk/dist/build.min.js) is strongly discouraged, as it poses security risks and may cause issues with minification. See https://github.com/rollup/rollup/wiki/Troubleshooting#avoiding-eval for more details
Why is eval used ? Isn’t there other solutions ?
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
How to prevent unsafe eval in a rollup bundle - Stack Overflow
I have csp header added from server side which doesn't contain script-src unsafe-eval . I even faced same issue in webpack but i...
Read more >rollup.js
Avoiding eval. You probably already know that ' eval is evil', at least according to some people. But it's particularly harmful with Rollup,...
Read more >How to Bundle JavaScript With Rollup — Step-by-Step Tutorial
Learn how to use Rollup as a smaller, more efficient alternative to webpack and Browserify to bundle JavaScript files in this step-by-step tutorial...
Read more >rollup.js
Introduction. Overview. Rollup is a module bundler for JavaScript which compiles small pieces of code into something larger and more complex, ...
Read more >Scope hoisting - Parcel
Avoid eval ... The eval function executes arbitrary JavaScript code in a string within the current scope. This means Parcel cannot rename any...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Guys you’re awesome ! Your customer service and relation with developers are really cool. 😉
@Gp2mv3 after looking into it a little more, we determined that this is most likely caused by using JSON.parse in a couple of locations. We have a safejson.parse method that should be used instead. We will do some testing and hopefully get this fixed in the next deploy. Thanks for notifying us on this!