-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
ES6 support? #21
Comments
Running through the same issue. It's saying that some packages are not being used and actually they are. I'm also assuming this is because of the ES6 syntax. As an example it's saying the package import routrPlugin from 'fluxible-plugin-routr'; |
Hey guys, I will look into it, ES6 support is definitely a must have. Thanks for taking the time to write an issue. |
I wonder if a more versatile approach would be to allow piping via stdin, then it would be possible to do something like |
I have this issue too. I started using React in my code recently. I run My requires are still traditional I'm not using depcheck directly. Instead I'm using |
👍 for es6 support in .js and .jsx |
👍 here. :) |
I think that the package detective-es6 can be leveraged to resolve this issue. |
+1 :) |
👍 |
👍 |
Hi, all. Because @rumpl don't response on my PR. I decide to publish my fork to NPM and rename to Modify your Personally, besides ES6 support, I am proposing supports for JSX and gulp. If anybody have some ideas, please open an issue in my fork. |
Store syntax-error files to invalidFiles property.
Hi all, I am back. 😃 Depcheck-es6 is merged back to original depcheck now. I have released version 0.5.9 on depcheck package in NPM. Thanks for @rumpl moving the repo under the org. I will continue to develop and maintain the project. |
Hi, and first of all thanks for a great piece of code.
Have you considered adding support for ES6 files – run via babel or traceur?
It should be as simple as looking for
import .+ from "<dependency>(/.+)?";
as well asrequire\("<dependency>(/.+)?"\);
.The text was updated successfully, but these errors were encountered: