We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug A clear and concise description of what the bug is.
I am seeing an issue with isDate() validation chain that sems to point to a recent fix not being propagated to npm registry.
Examples If applicable, add screenshots to help explain your problem.
npm registry and git master branch seem to be different.
I only checked isDate.js validator and the version on npm is missing a rectent fix. The code seems to be from prior branches.
Thanks,
Additional context Validator.js version: Node.js version: OS platform: [windows, linux, macOS, etc]
The text was updated successfully, but these errors were encountered:
Yes, master does not reflect our latest release but we have planned a new release that contains this fix. See #2269
Sorry, something went wrong.
now released, thanks! https://www.npmjs.com/package/validator/v/13.12.0
No branches or pull requests
Describe the bug
A clear and concise description of what the bug is.
I am seeing an issue with isDate() validation chain that sems to point to a recent fix not being propagated to npm registry.
Examples
If applicable, add screenshots to help explain your problem.
npm registry and git master branch seem to be different.
I only checked isDate.js validator and the version on npm is missing a rectent fix. The code seems to be from prior branches.
Thanks,
Additional context
Validator.js version:
Node.js version:
OS platform: [windows, linux, macOS, etc]
The text was updated successfully, but these errors were encountered: