dartness_server 0.6.1 dartness_server: ^0.6.1 copied to clipboard
Dartness is a framework for building efficient, scalable dart server-side applications. It provides an easy and quick way to develop modern standalone server.
We analyzed this package 12 days ago, and awarded it 120 pub points (of a possible 140):
10/10 points: Provide a valid pubspec.yaml
Issue tracker URL doesn't exist.
At the time of the analysis https://github.com/RicardoRB/dartness/issues
was unreachable. Make sure that the website is reachable via HEAD
requests.
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
188 out of 210 API elements (89.5 %) have documentation comments.
Some symbols that are missing documentation: dartness.InstanceRegister
, dartness.InstanceRegister.instance
, dartness.InstanceRegister.register
, dartness.InstanceRegister.resolve
, route.Controller.path
.
0/10 points: Package has an example
No example found.
See package layout guidelines on how to add an example.
20/20 points: Supports 5 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
- ✓ Android
- ✓ iOS
- ✓ Windows
- ✓ Linux
- ✓ macOS
These platforms are not supported:
Package not compatible with platform Web
Because:
package:dartness_server/dartness.dart
that imports:package:dartness_server/src/dartness.dart
that imports:package:dartness_server/src/server/log_requests_interceptor.dart
that imports:package:dartness_server/src/server/dartness_response.dart
that imports:dart:io
40/50 points: code has no errors, warnings, lints, or formatting issues
INFO: Dangling library doc comment.
lib/src/schedule/time_unit.dart:1:1
╷
1 │ ┌ /// A TimeUnit represents time durations at a given unit of granularity and provides utility methods
2 │ │ /// to convert across units, and to perform timing and delay operations in these units.
3 │ │ /// A TimeUnit does not maintain time information, but only helps organize and use time representations
4 │ │ /// that may be maintained separately across various contexts. A nanosecond is defined as one thousandth of a microsecond,
5 │ │ /// a microsecond as one thousandth of a millisecond, a millisecond as one thousandth of a second, a minute as sixty seconds,
│ └────────────────────────────────────────────────────────────────────────────────────────────^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/schedule/time_unit.dart
lib/src/schedule/time_unit.dart doesn't match the Dart formatter.
To format your files run: dart format .
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
collection |
^1.18.0 |
1.18.0 | 1.18.0 |
injector |
^3.0.0 |
3.0.0 | 3.0.0 |
shelf |
^1.4.1 |
1.4.1 | 1.4.1 |
shelf_plus |
^1.7.0 |
1.9.2 | 1.9.2 |
shelf_router |
^1.1.4 |
1.1.4 | 1.1.4 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
async |
- | 2.11.0 | 2.11.0 |
convert |
- | 3.1.1 | 3.1.1 |
crypto |
- | 3.0.3 | 3.0.3 |
hotreloader |
- | 4.2.0 | 4.2.0 |
http_methods |
- | 1.1.1 | 1.1.1 |
http_parser |
- | 4.0.2 | 4.0.2 |
logging |
- | 1.2.0 | 1.2.0 |
meta |
- | 1.14.0 | 1.14.0 |
mime |
- | 1.0.5 | 1.0.5 |
mime_type |
- | 1.0.0 | 1.0.0 |
path |
- | 1.9.0 | 1.9.0 |
shelf_hotreload |
- | 1.5.0 | 1.5.0 |
shelf_static |
- | 1.1.2 | 1.1.2 |
shelf_web_socket |
- | 1.0.4 | 1.0.4 |
source_span |
- | 1.10.0 | 1.10.0 |
stack_trace |
- | 1.11.1 | 1.11.1 |
stream_channel |
- | 2.1.2 | 2.1.2 |
stream_transform |
- | 2.1.0 | 2.1.0 |
string_scanner |
- | 1.2.0 | 1.2.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
typed_data |
- | 1.3.2 | 1.3.2 |
vm_service |
- | 14.2.1 | 14.2.1 |
watcher |
- | 1.1.0 | 1.1.0 |
web |
- | 0.5.1 | 0.5.1 |
web_socket_channel |
- | 2.4.5 | 2.4.5 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
10/10 points: Package supports latest stable Dart and Flutter SDKs
Analyzed with Pana 0.22.3
, Dart 3.3.3
.
Check the analysis log for details.