-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vue is not defined after build #321
Comments
you can load your plugin in a regular entry instead, like |
the Maybe we can check if the input file exports a |
Thank you @egoist for the direction. I went with the example folder and now I have a logical development env for Vue plugins. I think it'd be great to have Maybe I'm wrong, but the
|
hmm what's the problem here?
If you're not using the default entry you can install plugin in your own entry file. I use |
I have this file as an entry for my Vue project.
When I run
and then run the output in the browser I can't access the Vue object, even though the warning from
vue.runtime.common.js
indicates that the Vue object is present.Nowhere in my project I don't import the Vue module, because I'm writing a plugin. So it's somehow unclear how
vue.runtime.common.js
is present?Morevoer, because
vue.runtime.common.js
is present I expect that Vue object is defined onwindow
, but it isn't.Please see the picture below for more info:
Can someone explain what is happening during the build process?
The text was updated successfully, but these errors were encountered: