You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could someone please help me understand why switching content-script to use format: ['es'] breaks Vue usage in the extension? 😕
At a high level, it looks like importing vue ends up writing all vars and functions to window. I don't know why changing to 'es' would cause this. you can see on the right side, under Scope, that the window object appears to have APIs such as createApp, createHook etc.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Could someone please help me understand why switching content-script to use
format: ['es']
breaks Vue usage in the extension? 😕At a high level, it looks like importing vue ends up writing all
vars
and functions towindow
. I don't know why changing to 'es' would cause this. you can see on the right side, under Scope, that the window object appears to have APIs such ascreateApp
,createHook
etc.Beta Was this translation helpful? Give feedback.
All reactions