Yeah, so I have looked into it, and the way around it is to switch from Vue.esm to Vue.runtime... which will only work if the templates have been designed in a certain way
I don't think the CSP can be avoided
it won't be avoided 😄
are you using webpack?
for dev or prod build?
Prod I believe, but null went to bed (rightfully so, it's getting late)
@flamerohr i'm using Webpack
Generating a production build and hitting said issue 🙂
I haven't used vue directly with this, so I'm not sure if vue is responsible for its own evals (I've found this that could help https://stackoverflow.com/a/34621858 )
But webpack tries to polyfill node.js functions, which you could try turning off with
node: false at the top-level of your webpack config