-
Notifications
You must be signed in to change notification settings - Fork 98
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
getting runtime-only build #14
Comments
the issue is that you're using runtime only package. |
Thanks for the speedy reply. |
Is this due to a change in the 3.0 code ? |
I jumped from Maybe I was wrong. |
Thanks. I don't know enough of Vue to give any advice, other than the downside of the added size if you include the compiler. For others having this issue, I was able to get going again with this change in Webpack:
Thanks for an awesome package. |
I have the same issue here and would like to use vue-snotify with runtime-only builds. |
working on this. |
@artemsky Thanks. We really need this. It's the only reason why we currently don't use vue-snotify on some projects. |
@arenddeboer I used your fix and it's working properly now. Could you please explain what does that line of code do? Also, thank you @artemsky for the great package |
@gpuma have a look at the docs here: https://vuejs.org/v2/guide/installation.html#Explanation-of-Different-Builds it has a section about the different builds and how to include them in webpack |
Any luck with this ? :) |
I'm new to Vue, and this doesn't seem to work out of the box with my vue-cli 3 template. @artemsky maybe the project needs to be updated to support it? Just thinking out loud, as I have not yet found a good solution for it that doesn't include providing webpack resolve aliases for pretty much everything. Compilation fails otherwise. edit:
|
Please help! Cannot get it to work either. I use a Vue-cli3 project. What am I doing wrong?
I tried all fixes, the only thing that is happening is |
Runtime build ready |
@artemsky thank you... missed that completely... Are you going to make a new release? Or, how can I update to get the runtime? |
Same as @erodewald, if using the vue.config.js, you can also add it to the configureWebpack object as follows(this took me forever to find): EXAMPLE: module.exports = {
configureWebpack: {
resolve: {
alias: {
'vue$': 'vue/dist/vue.esm.js'
}
},
},
} |
If you use the NPM way of importing vue-snotify, then the vue.config.js addition is not needed. |
i have the same issue how to fix it getting this error when run
i get this error
|
@focussing I added |
Still got this issue even with v3.2.1
|
|
Hi. Great looking package here. I'm trying to use it in a vue app, but when I include the component in my App.vue, I get a warning saying:
In my main.js, i have:
And in App.vue, I put in:
Any ideas on what I may be doing wrong?
The text was updated successfully, but these errors were encountered: