Breaking Changes in v4.2.0
See original GitHub issuevar Recaptcha = require('express-recaptcha').Recaptcha;
var recaptcha = new Recaptcha('xxx', 'xxx');
This code works in 4.1.1, but throws an error on 4.2.0.
Version 4.2.0 requires adding the V2
.
var Recaptcha = require('express-recaptcha').RecaptchaV2;
This is a breaking change, so you should change the version number to 5.0.0 for this release. You should also release an update to 4.2.1 with this change reversed, to help people who depend on your package working as it usually did.
Please see the npm documentation page about semantic versioning for more information.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Breaking Changes · microsoft/TypeScript Wiki - GitHub
These changes list where implementation differs between versions as the spec and compiler are simplified and inconsistencies are corrected. For ...
Read more >ASP.NET 4 Breaking Changes | Microsoft Learn
This document describes changes that have been made for the .NET Framework version 4 release that can potentially affect applications that ...
Read more >c# - Breaking changes in .NET 4.0 - Stack Overflow
Breaking changes in .NET 4.0 · Timespan now implements IFormattable and old string. · Access to events inside the class where they are...
Read more >Migrating from v3 to v4 - Gatsby
This section explains breaking changes that were made for Gatsby 4. Some of those changes had a deprecation message in v3. In order...
Read more >Release notes v4.2.0 - Alfresco Builder Network
This is a minor release of the Alfresco Application Development Framework, developed to receive the latest and greatest benefits of the bugfixes and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Wow, that was quick. Great work on the fix and on this package in general. Thanks!
Thank you men !