I use your great react-bootstrap-typeahead. So - it is awesome :-).
And now after React.js 15.5.4 was installed I got warnings:
Do you plan to upgrade your code?
https://facebook.github.io/react/blog/
Thank you in advance for an answer.
Maybe I just need do something.
Thanks for the report. Note that these are simply deprecation warnings in anticipation of React 16 and won't cause any errors... yet. Fixing these warnings is on my to-do list, I just need to get around to it :)
@ericgio
Fixed deprecations for the module and updated some dependencies.
Though, there is the same problem with https://github.com/helior/react-highlighter/ dependency yet.
But I think the PR can be merged at the moment.
@lunochkin don't get it, are the deprecations fixed? Still getting them on my side.
@BillOTei Those changes are not released yet see #181
Oh i see thx.
2017-06-07 11:46 GMT+02:00 Matthieu Lemoine notifications@github.com:
@BillOTei https://github.com/billotei These changes are not release yet
see #181 https://github.com/ericgio/react-bootstrap-typeahead/pull/181—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ericgio/react-bootstrap-typeahead/issues/168#issuecomment-306746099,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACNKqnfTaOkM-vywrXvgls7ryeKAhH1mks5sBnF6gaJpZM4NCy2z
.
--
__________________________
!\_________________________/!\
!! !! \
!! fsociety: ALX-DEV~$ !! \
!! Alexandre Teilhet~$ !! !
!! Web Developer~$ !! !
!! +33 6 03 9092 71~$ !! !
!! linkedin
https://www.linkedin.com/in/alexandre-teilhet-7aa71483
!! !
!! !! !
!! !! /
!!_________________________!! /
!/_________________________!/
___________________/__/!
!_______________________!/
________________________
/oooo oooo oooo oooo /!
/o#mrrobotoooooooooooooo/ /
/ooooooooooooooooooooooo/ /
/_______________________/_/
It seems that now all dependencies are without such problem, so new release can be published.
Installed today and still get the same errors
Fixed in v1.4.0. Sorry for the delay.
Thank you
Most helpful comment
Thanks for the report. Note that these are simply deprecation warnings in anticipation of React 16 and won't cause any errors... yet. Fixing these warnings is on my to-do list, I just need to get around to it :)