I’m debugging a Solid app using my solid-safe-client library in SAFE Browser.
As far as I can see none of the app code or dependencies are using window.eval but SAFE Browser is complaining about it, saying ‘Sorry, peruse does not support window.eval()’.
Uncaught Error: Sorry, peruse does not support window.eval().
at window.eval.global.eval (/home/mrh/safe-releases/2017-09-21_Alpha_2/safe-browser-v0.11.2-linux-x64-dev/resources/app.asar/app/webPreload.prod.js:sourcemap:1)
at Object../node_modules/react-dev-utils/webpackHotDevClient.js (0.chunk.js:5312)
at __webpack_require__ (bundle.js:782)
at fn (bundle.js:150)
at Object.0 (main.chunk.js:750)
at __webpack_require__ (bundle.js:782)
at checkDeferredModules (bundle.js:46)
at Array.webpackJsonpCallback [as push] (bundle.js:33)
at main.chunk.js:1
From this it looks like I’m encountering it in the React dev tools / hot relaod area. Does this seem likely. I’m running using npm start in the root of the Solid app (solid-filemanager).
I think that would help, but if this were changed in Dev build that would be ideal (even if opt-in with a setting). I filed an issue yesterday requesting that.
I haven’t created a repo for the app yet, but think if you use the unadulterated app below you will see the issue. You will get some other errors, and cause a Google fonts page to open in an http browser, but I have checked that this doesn’t interfere with the running of my version of this app, and the changes I made are trivial.
If using that doesn’t work let me know and I’ll push my code.