Rafee Memon

Use the `readOnly` prop: https://github.com/Hacker0x01/react-datepicker/blob/master/docs/datepicker.md EDIT (Sept. 19, 2018): This behavior changed with https://github.com/Hacker0x01/react-datepicker/pull/1419, and this is no longer valid.

Reopening, as this behavior changed in #1419

Perhaps a less intrusive solution would be to add a configuration option to `node { ... }` that would toggle the behavior of the `npmInstall` task. This could be toggled...

Perhaps a solution to this could be to only consider `package.json` files in `node_modules` in the outputs rather than the entire directory (re: [this line](https://github.com/srs/gradle-node-plugin/blob/v1.2.0/src/main/groovy/com/moowork/gradle/node/npm/NpmInstallTask.groovy#L19)). I'm not sure if this...

@g3force > We actually do have the package-lock.json checked in, but the CI build unpredictably modifies it during npm install. That invalidates the cache on the second run. You probably...

> npm ci removes the node_modules completely. That is not, what I want in an incremental build. In our build-pipeline, I always do a clean build which removes the node_modules...

The task will be _checked_, but not run, if package.json, package-lock.json, and node_modules haven't changed. The build pipeline should be relevant -- if you're getting unpredictable lock file modifications on...

Here is my workaround (on Windows): For running tasks during development outside of the normal build flow (such as `npm start`, `npm install`) I use a wrapper batch file that...