Skip to content
Discussion options

You must be logged in to vote

If you have publish_to: none, it doesn't make much a difference whether a package is in dependencies or dev_dependencies.

Technically, drift_dev is only used for development, so dev_dependencies would be the correct way to put it. But for some migration-validation APIs that are in drift_dev, it's possible that you need to import it into lib/. These typically would only be used on debug builds (so technically during development only), but the linter can't know that and reports a warning anyway. So putting drift_dev into dependencies to avoid that issue causes no harm whatsoever.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by homeserve-lsaudon
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants