flutter_razorpay_web 0.0.3
flutter_razorpay_web: ^0.0.3 copied to clipboard
Package for razorpay web is designed to facilitate smooth integration of Razorpay's payment gateway services specifically for web-based Flutter applications.
We analyzed this package 4 days ago, and awarded it 80 pub points (of a possible 160):
10/10 points: Provide a valid pubspec.yaml
5/5 points: Provide a valid README.md
5/5 points: Provide a valid CHANGELOG.md
10/10 points: Use an OSI-approved license
Detected license: MIT.
10/10 points: 20% or more of the public API has dartdoc comments
18 out of 68 API elements (26.5 %) have documentation comments.
Some symbols that are missing documentation: flutter_razorpay_web, js_razorpay, js_razorpay.JsRazorpay, js_razorpay.JsRazorpay.JsRazorpay.new, js_razorpay.JsRazorpay.close.
10/10 points: Package has an example
20/20 points: Supports 1 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
- ✓ Web
These platforms are not supported:
Package does not support platform `Android`.
Because:
package:flutter_razorpay_web/flutter_razorpay_web.dartthat declares support for platforms:Web.
Package does not support platform `iOS`.
Because:
package:flutter_razorpay_web/flutter_razorpay_web.dartthat declares support for platforms:Web.
Package does not support platform `Windows`.
Because:
package:flutter_razorpay_web/flutter_razorpay_web.dartthat declares support for platforms:Web.
Package does not support platform `Linux`.
Because:
package:flutter_razorpay_web/flutter_razorpay_web.dartthat declares support for platforms:Web.
Package does not support platform `macOS`.
Because:
package:flutter_razorpay_web/flutter_razorpay_web.dartthat declares support for platforms:Web.
0/50 points: code has no errors, warnings, lints, or formatting issues
Found 9 issues. Showing the first 2:
ERROR: The method 'jsify' isn't defined for the type 'JsRazorpay'.
lib/razorpay_web/js_razorpay.dart:11:11
╷
11 │ jsify(options),
│ ^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/razorpay_web/js_razorpay.dart
ERROR: The method 'allowInterop' isn't defined for the type 'JsRazorpay'.
lib/razorpay_web/js_razorpay.dart:14:13
╷
14 │ allowInterop(onFailed),
│ ^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/razorpay_web/js_razorpay.dart
0/10 points: All of the package dependencies are supported in the latest version
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
js |
^0.6.7 |
0.6.7 | 0.7.2 | Discontinued |
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
characters |
- | 1.4.0 | 1.4.1 | |
collection |
- | 1.19.1 | 1.19.1 | |
material_color_utilities |
- | 0.11.1 | 0.13.0 | |
meta |
- | 1.17.0 | 1.17.0 | |
vector_math |
- | 2.2.0 | 2.2.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides.
The constraint `^0.6.7` on js does not support the stable version `0.7.0`.
Try running dart pub upgrade --major-versions js to update the constraint.
The package has one or more discontinued direct dependencies.
Discontinued packages are no longer maintained, and can end up being a
liability.
Consider migrating away from these dependencies:
- js.
10/10 points: Package supports latest stable Dart and Flutter SDKs
0/20 points: Compatible with dependency constraint lower bounds
downgrade analysis failed failed with 4 errors:
UNDEFINED_METHOD-lib/razorpay_web/js_razorpay.dart:11:11- The method 'jsify' isn't defined for the type 'JsRazorpay'.UNDEFINED_METHOD-lib/razorpay_web/js_razorpay.dart:14:13- The method 'allowInterop' isn't defined for the type 'JsRazorpay'.UNDEFINED_METHOD-lib/razorpay_web/razorpay_web.dart:100:26- The method 'allowInterop' isn't defined for the type 'RazorpayWeb'.
Run flutter pub downgrade and then flutter analyze to reproduce the above problem.
You may run dart pub upgrade --tighten to update your dependency constraints, see dart.dev/go/downgrade-testing for details.
Analyzed with Pana 0.23.5, Flutter 3.38.5, Dart 3.10.4.
Check the analysis log for details.