Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include the names of each special in the README #206

Merged
merged 2 commits into from
Jul 21, 2017

Conversation

rouanw
Copy link
Contributor

@rouanw rouanw commented Mar 16, 2017

to make it easier to find which options to pass to depcheck.

I couldn't find the Grunt special in the codebase - does it still exist?

to make it easier to find which options to pass to `depcheck`.

I couldn't find the Grunt special in the codebase - does it still exist?
@rouanw
Copy link
Contributor Author

rouanw commented Mar 16, 2017

The build failure appears unlinked to my changes to the README:

AssertionError: [ 'cross-env' ] deepEqual []
    at /home/travis/build/depcheck/depcheck/build/check-json.js:27:12
    at check (/home/travis/build/depcheck/depcheck/build/check-json.js:25:10)
    at _callee$ (/home/travis/build/depcheck/depcheck/build/check-json.js:46:3)
    at tryCatch (/home/travis/build/depcheck/depcheck/node_modules/regenerator-
# ...
The command "npm run depcheck-json" exited with 1.

Can someone more familiar with the code please take a look? I get the same failure locally on master (node 6.9.1).

@rouanw rouanw changed the title Include the names of each special to the README Include the names of each special in the README Mar 16, 2017
@rouanw
Copy link
Contributor Author

rouanw commented Apr 28, 2017

@lijunle will you please take a look? 🔦

@haggholm
Copy link
Contributor

Ditto, blocking #205.

It seems that depcheck is in fact failing to detect all of its own dependencies(!); the test-coverage npm script uses node_modules/.bin/cross-env, but (I suppose) because cross-env is never required by any JS code, it isn’t recognised as a dependency—hence, depcheck fails its own check.

This can be fairly easily worked around by changing

  "scripts": {
    // ...
    "depcheck": "node ./bin/depcheck",
    // ...
  },

to

  "scripts": {
    // ...
    "depcheck": "node ./bin/depcheck --ignores=cross-env",
    // ...
  },

but it feels a bit dirty to have a workaround for depcheck in depcheck itself...

Copy link
Member

@lijunle lijunle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good! Sorry for my late to review.

@codecov
Copy link

codecov bot commented Jul 21, 2017

Codecov Report

Merging #206 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #206   +/-   ##
=======================================
  Coverage   98.14%   98.14%           
=======================================
  Files          24       24           
  Lines         432      432           
=======================================
  Hits          424      424           
  Misses          8        8

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1a675b4...b661a62. Read the comment docs.

@lijunle lijunle merged commit 974a779 into depcheck:master Jul 21, 2017
@rouanw rouanw deleted the patch-1 branch July 21, 2017 14:42
@rouanw
Copy link
Contributor Author

rouanw commented Jul 21, 2017

Thanks @lijunle 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants