Skip to content

Conversation

@christiantinauer
Copy link

@christiantinauer christiantinauer commented Sep 15, 2017

…s to deps, because they are used to make react-selectize work in production. PeerDependencies force the user to also use the same exact versions, which is a problem with react-transition-group (v1 and v2 do exist).

@coveralls
Copy link

Coverage Status

Coverage remained the same at 88.316% when pulling 23f048c on christiantinauer:master into d3f7072 on furqanZafar:master.

…s to deps, because they are used to make react-selectize work in production. PeerDependencies force the user to also use the same exact versions, which is problem with react-transition-group (v1 and v2 do exist).
@martinkutter
Copy link

+1

@iulianraduat
Copy link

Can someone please approve this pull request? I cannot use react-selectize with React 16 as the dependencies force me to have React 15 also. Thanks

@martinkutter
Copy link

This pull request is now open for more than one month, without comment from the project owners. This is not ok for a library I want to use in production. Is this project still under maintenance?

@jwalton
Copy link

jwalton commented May 30, 2018

I published a fork with this fixed: https://www.npmjs.com/package/@benbria/react-selectize

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

Successfully merging this pull request may close these issues.

5 participants