Issues found
Based on crates you own that have been published to crates.io. The best way to monitor these issues is to subscribe to the atom feed in your RSS reader.
mu-sdk-macros
Imprecise dependency requirement syn = 2
Cargo does not always pick latest versions of dependencies! Specify the version as
syn = "2.0.100"
. IfCargo.lock
ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using theminimal-versions
flag, used by users of old Rust versions.This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.
No readme property
Specify path to a
README
file for the project, so that information about is included in the crates.io tarball.
css-loader
No repository property
Specify git repository URL in
Cargo.toml
to help users find more information, contribute, and for lib.rs to read more info.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["web-programming"]
to theCargo.toml
.Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.
Missing keywords
Help users find your crates. Add
keywords = ["css-loader", "scoping", "loader", "sass", "function-component"]
(up to 5) to theCargo.toml
. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.
css-loader-macros
No repository property
Specify git repository URL in
Cargo.toml
to help users find more information, contribute, and for lib.rs to read more info.Dependency cssparser 0.29 is significantly outdated
Upgrade to 0.35.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Dependency syn 1 is significantly outdated
Upgrade to 2.0.100 to get all the fixes, and avoid causing duplicate dependencies in projects.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.Imprecise dependency requirement syn = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
syn = "2.0.100"
. IfCargo.lock
ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using theminimal-versions
flag, used by users of old Rust versions.Dependency rsass 0.25 is outdated
Upgrade to 0.29.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
No issues found in: mu-cli mu-sdk
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.