Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
dist/print.js is bloated with eval()
See original GitHub issueIn 1.0.63, code in dist/print.js ( see from unpkg ) contains eval().
It seems some build settings of Webpack might be inaccurate for distribution build.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Why is using the JavaScript eval function a bad idea?
Improper use of eval opens up your code for injection attacks. Debugging can be more challenging (no line numbers, etc.) eval'd code executes...
Read more >EvalError - JavaScript - MDN Web Docs - Mozilla
EvalError is a serializable object, so it can be cloned with structuredClone() or copied between Workers using postMessage() . Constructor.
Read more >JavaScript eval() Method - W3Schools
If the argument is an expression, eval() evaluates the expression. If the argument is one or more JavaScript statements, eval() executes the statements....
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 Free
Top 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
Sorry for the delay guys. @natalan I thought I used the
productionflag. But maybe I messed this up. I just merged your PR. Will run a few manual tests and try to publish a new version as soon as possible.Closing this since these changes were deployed to npm. Latest version is currently v1.1.0. Thank you.