Request - Update npm package to include latest changes

[JonShort]

Table of Contents

• Expected Behavior
• Current Behavior
• Possible Solution
• Steps to Reproduce (for bugs)
• Context
• Your Environment

Expected Behavior

Version of the npm package should be updated from 5.1.0 (current) to 5.1.1

Current Behavior

Currently, version 5.1.0 contains a few bugs, most notably the proptypes warnings that are thrown when the component is used in React 15.

Possible Solution

Updating the npm package to 5.1.1 will include the following bugfixes:

• Fixing duplicate key warning when minDate or maxDate #131 - Fix to duplicate key warning when using minDate or maxDate
• Replaced React.PropTypes reference with PropTypes #133 - Fix to remove proptypes warnings (now more important given React 16 is releasing soon)
• Fix "Cannot read property 'slice' of undefined" bug with min/max dates #137 - Fix to bug when using minDate or maxDate

As a further enhancement, the updating of the npm package could be added to the CI build, triggered when version patched. But this is not necessary to address this issue.

Steps to Reproduce (for bugs)

N/A

Context

This component is throwing proptypes warnings in unit tests & development in projects me & my team are working on.

I am also aware that members of the community have had to resort to using their own forks to fix the bugs associated with minDate and maxDate.

Your Environment

N/A

[noushad-pp]

When will this npm package be upadated?

[vivek1623]

plz fix it soon, i am facing same issues.

[juanpaco]

React 16 has landed, and the PropTypes issue prevents upgrading to React 16.

[aanguswilliams]

@wehriam is there anything we can do to help get these fixes published?

[JonShort]

For those struggling with the PropTypes warnings, I've added a CI config to my fork of this repo to publish an npm package with the latest changes.

This is for my own personal use, and i recommend not using it, but if you really need to fix the propTypes warnings feel free to use my npm package.

I'm hoping it'll be a temporary solution for me.

[flygis]

Please update the npm package so we all can move on with our life. The wait has been long enough for this.

[redheadedstep]

Well, I just wasted 4 hours tracking down #131 only to discover that the npm package hasn't been updated from 5.1.0 to 5.1.1. Can you just run the command line, update npm, and save us all a lot of headache!?

Other than that, great tool and very easy to implement.

[travellingprog]

I know it's not an ideal solution, but we got past this by just pointing to the latest commit of this repo. In our package.json, we have react-bootstrap-date-picker set to "github:pushtell/react-bootstrap-date-picker#f622dc8872dd180324ba5d3c295d009848f5814b". An NPM or Yarn install will be able to understand that.

[asazernik]

@pushtell Have you seen this?

[Crisfole]

Bump. At very least we need min/max date bugfix.

[filipetedim]

Bump. It's literally running one line. Maybe something happened to @pushtell ?

[winstonewert]

Do we need to fork?

[JonShort]

Yeah unfortunately you'll need to fork it, or use one of the forks that others have made 👍

[winstonewert]

Has anyone tried to put together a fork which aims to supplant the original? Or is everyone just making a bunch of random forks?