-
Notifications
You must be signed in to change notification settings - Fork 252
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
new fork, react-dropdown-now #183
Comments
Nice work @iambumblehead |
Thanks, but the important changes there are mostly from @lwhiteley |
A little update on react-dropdown-now,
|
I'm sure I'm misunderstanding something, but I installed this into my react-app and yarn run start no longer worked. |
@travisddraper if you make a little package that demonstrates the problem, I'll take a look to try and resolve it. |
@travisddraper react-dropdown-now is updated with changes that may resolve the issue you were having |
With humble respect to @fraserxu I have published a fork of react-dropdown named react-dropdown-now. The reason for a fork is, this repository seems unmaintained and its sources need updates to remain usable. For example, recent versions of react log noisy messages about react-dropdown's usage of deprecated lifecycle hooks.
I'm interested to further stabilize the forked dropdown and to accept pull requests needed by other users. Small improvements are already found in the react-dropdown-now fork,
npm install
does not result in audit warningsThe text was updated successfully, but these errors were encountered: