The weeder package

[Tags:bsd3, program]

Find redundant package dependencies or redundant module exports.


[Skip to Readme]

Properties

Versions 0.1, 0.1.1, 0.1.2, 0.1.3
Change log CHANGES.txt
Dependencies aeson, base (>=4.6 && <5), bytestring, cmdargs, extra, filepath, hashable, process (>=1.2.3.0), text, unordered-containers, vector, yaml [details]
License BSD3
Copyright Neil Mitchell 2017
Author Neil Mitchell <ndmitchell@gmail.com>
Maintainer Neil Mitchell <ndmitchell@gmail.com>
Category Development
Home page https://github.com/ndmitchell/weeder#readme
Bug tracker https://github.com/ndmitchell/weeder/issues
Source repository head: git clone https://github.com/ndmitchell/weeder.git
Uploaded Fri Apr 28 20:23:20 UTC 2017 by NeilMitchell
Updated Sat Apr 29 14:22:17 UTC 2017 by AdamBergmark to revision 1
Distributions NixOS:0.1.2, Stackage:0.1.3
Downloads 118 total (118 in the last 30 days)
Votes
0 []
Status Docs not available [build log]
Last success reported on 2017-04-28 [all 3 reports]

Downloads

Maintainer's Corner

For package maintainers and hackage trustees

Readme for weeder

Readme for weeder-0.1

Weeder Hackage version Stackage version Linux Build Status Windows Build Status

The principle is to delete dead code (pulling up the weeds). To do that, run:

  • GHC with -fwarn-unused-binds -fwarn-unused-imports, which finds unused definitions and unused imports.
  • HLint, looking for "Redundant extension" hints, which finds unused extensions.
  • This tool, weeder . which detects redundant build-depends in the .cabal and functions that are exported internally but not available outside this library.

To use weeder your code must be building with stack, as it piggy-backs off some files stack generates. If you don't normally build with stack a simple stack init && weeder . --build is likely to be sufficient.