How to resolve `unsafe-eval` issues for extension development

[jonahlibrach]

I'm getting some

How do I resolve these issues when building the app with webpack? Is it a simple modification to the dev.config.babel.js?

Albeit unsuccessfully, I tried to follow what was recommended here: https://stackoverflow.com/questions/48047150/chrome-extension-compiled-by-webpack-throws-unsafe-eval-error

Has anyone encountered this before? How to move forward and get it working?

[Methuselah96]

Try un-commenting this line in the base config. I don't have time to check if that works right now, but I'll take a look later.

[jonahlibrach]

Doing that caused this:

[hecjhs]

@Methuselah96 did you have any chance to check what's going on, I'm getting the same error

[Methuselah96]

Is this causing the DevTools to not work? I get the first error when I go to GitHub with the dev build, but the DevTools still seem to work for sites that have the extension enabled.

[Methuselah96]

@jonahlibrach Also, just to confirm, are you using Yarn? This repository only works with Yarn.

[Methuselah96]

@jonahlibrach @hecjhs Were you able to check whether this was causing the DevTools to not work?

[Methuselah96]

I'm going to go ahead and close this, but feel free to reply if you have any new information to help reproduce this issue and I can reopen it.

[hecjhs]

@Methuselah96 I'm still having issues with this, can you provide documentation on how I should run this on dev mode?

[Methuselah96]

Is this causing the DevTools to not work? I get the first error when I go to GitHub with the dev build, but the DevTools still seem to work for sites that have the extension enabled.

[hecjhs]

yes, when I load the extension on dev mode as is suggested here, the DevTools is not working, so I've tried to change this line as you suggested, but I have no luck with that