Skip to content

Vue 2.0 support #19

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

Closed
magne4000 opened this issue Oct 4, 2016 · 10 comments
Closed

Vue 2.0 support #19

magne4000 opened this issue Oct 4, 2016 · 10 comments

Comments

@magne4000
Copy link

Is there any plan on supporting new version 2.0 of Vue.js ?

@beeplin
Copy link

beeplin commented Oct 4, 2016

+1~

amcsi added a commit to amcsi/vue-dragula that referenced this issue Oct 9, 2016
@amcsi
Copy link
Contributor

amcsi commented Oct 9, 2016

I have created a PR to support (only) Vue 2.0
Here is the PR: #22

In the meantime you could use the vue2-build branch from my own fork as a temporary solution:
https://github.com/amcsi/vue-dragula/tree/vue2-build

EDIT: I have also updated my above vue2-build to also support both VueJS 1.0 and 2.0

Astray-git added a commit that referenced this issue Oct 10, 2016
@Astray-git
Copy link
Owner

1.3.0 released with #22

@amcsi
Copy link
Contributor

amcsi commented Oct 10, 2016

@Astray-git when I used npm build, not just the minified js, but a non-minified dist js file was also built. But in your release commit you only added the minified js. Did you maybe forget to add the non-minified dist js?

@Astray-git
Copy link
Owner

1acafab
You mean this one? There are 3 changed files.

@amcsi
Copy link
Contributor

amcsi commented Oct 11, 2016

Oh silly me, i had that dist file there mixed up with the source file in my head. Never mind!

@amcsi
Copy link
Contributor

amcsi commented Oct 14, 2016

@Astray-git It seems the latest version hasn't yet been published to npm. Is that normal?

@Astray-git
Copy link
Owner

@amcsi 😅 Sorry , I forgot to publish it.

@deiucanta
Copy link

I just tried this in Vue 2.0 and the list doesn't seem to order. I assume it conflicts with the virtual dom.

@amcsi
Copy link
Contributor

amcsi commented Oct 17, 2016

@deiucanta please create a new issue for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants