I am working with Cypress for writing automation tests for a website.
I'm facing a problem in that my custom commands, which I'm adding in the 'cypress/support/commands.js' file, are not recognised by Webstorm in the test bodies.
However, once I run the actual tests, everything works as needed, so for some reason it's just the webstorm that can't read it correctly.
I've read online and tried the common fix of adding "supportFile": "cypress/support/index.js" to the cypress.json, but it didn't work for me.
I'd like some input and help. Thanks in advance!
Visualization of the issue
A primary method to get your IDE to know about your custom command is to use TypeScript definitions. Refer to the Cypress docs for details.
For IntelliJ platform, there is a Cypress Support Pro paid plugin (I'm the author) that simplify managing TypeScript definitions for custom commands. See this overview:
In order to refactor a client-side project, i'm looking for a safe way to find (and delete) unused code.
What tools do you use to find unused/dead code in large react projects? Our product has been in development for some years, and it is getting very hard to manually detect code that is no longer in use. We do however try to delete as much unused code as possible.
Suggestions for general strategies/techniques (other than specific tools) are also appreciated.
Thank you
Solution:
For node projects, run the following command in your project root:
npx unimported
If you're using flow type annotations, you need to add the --flow flag:
npx unimported --flow
Source & docs: https://github.com/smeijer/unimported
Outcome:
Background
Just like the other answers, I've tried a lot of different libraries but never had real success.
I needed to find entire files that aren't being used. Not just functions or variables. For that, I already have my linter.
I've tried deadfile, unrequired, trucker, but all without success.
After searching for over a year, there was one thing left to do. Write something myself.
unimported starts at your entry point, and follows all your import/require statements. All code files that exist in your source folder, that aren't imported, are being reported.
Note, at this moment it only scans for source files. Not for images or other assets. As those are often "imported" in other ways (through tags or via css).
Also, it will have false positives. For example; sometimes we write scripts that are meant to simplify our development process, such as build steps. Those aren't directly imported.
Also, sometimes we install peer dependencies and our code doesn't directly import those. Those will be reported.
But for me, unimported is already very useful. I've removed a dozen of files from my projects. So it's definitely worth a shot.
If you have any troubles with it, please let me know. Trough github issues, or contact me on twitter: https://twitter.com/meijer_s
Solution for Webpack: UnusedWebpackPlugin
I work on a big front-end React project (1100+ js files) and stumbled upon the same problem: how to find out which files are unused anymore?
I've tested the next tools so far:
findead
deadfile
unrequired
None of them really worked. One of the reason is that we use "not standard" imports. In additional to the regular relative paths in our imports we also use paths resolved by the webpack resolve feature which basically allows us to use neat import 'pages/something' rather than cumbersome import '../../../pages/something'.
UnusedWebpackPlugin
So here is the solution I've finally come across thanks to Liam O'Boyle (elyobo) #GitHub:
https://github.com/MatthieuLemoine/unused-webpack-plugin
It's a webpack plugin so it's gonna work only if your bundler is webpack.
I personaly find it good that you don't need to run it separately but instead it's built into your building process throwing warnings when something is not ok.
Our research topic: https://github.com/spencermountain/unrequired/issues/6
Libraries such as unrequired and deadcode only support legacy code.
In order to find the unused assets, to remove manually, you can use deadfile
library:https://m-izadmehr.github.io/deadfile/
Out of box support for ES5, ES6, React, Vue, ESM, CommonJs.
It supports import/require and even dynamic import.
It can simply find unused files, in any JS project.
Without any config, it supports ES6, React, JSX, and Vue files:
First of all, very good question, in large project coders usually try many lines of code test and at the end of result, hard to find the unused code.
There is two possible that must be work for you - i usually do whenever i need to remove and reduce the unused code into my project.
1st way WebStorm IDE:
If you're using the web-storm IDE for JS development or React JS / React Native or Vue js etc it's tell us and indicate us alote of mention with different color or red warning as unused code inside the editor
but it's not works in your particular scenario there is another way to remove the unused code .
2nd Way unrequired Library: (JSX is not supported)
The second way to remove the unused code inside the project is unrequired library you can visit here : unrequired github
another library called depcheck under NPM & github here
Just follow their appropriate method - how to use them you will fix this unused issue easily
Hopefully that helps you
I think the easiest solution for a create-react-app bootstrapped application is to use ESLint. Tried using various webpack plugins, but ran into out of memory issues with each plugin.
Use the no-unused-modules which is now a part of eslint-plugin-import.
After setting up eslint, installing eslint-plugin-import, add the following to the rules:
"rules: {
...otherRules,
"import/no-unused-modules": [1, {"unusedExports": true}]
}
My approach is an intensive use of ESlint and make it run both on IDE ad before every push.
It points out unused variables, methods, imports and so on.
Webpack (which has too nice plugins for dead code detection) take care about avoiding to bundle unimported code.
findead
With findead you can find all unused components in your project. Just install and run:
Install
npm i -g findead
Usage
findead /path/to/search
This question recalls me that react by default removes the deadcode from the src when you run the build command.
Notes:
you need to run build command only when you want to ship your app to production.
Im trying to uglify a script with code kit that contains references to async functions but I'm having to transpile it with babel in order for it to work. However after checking the console on my site I get smacked with an error 'regeneratorRuntime is not defined' where the arrow functions are supposed to be.
Now I've done a lot of googling and everyone points to do something with npm which I'm not familiar with at all. Is there any settings in codeKit I am missing or require to do in order for it to work.
If not, please could you explain like I'm five how to fix this issue through npm.
Big thanks in advance!
Your Codekit Babel configuration seems to be wrong.
Arrow functions are implemented since ES2015 and async functions since ES2017.
You should activate related plugins in case you targeted old browsers.
I'm using Atom editor, and it runs javascript test with Jasmine for ES6, with functionalities that are not read by any browser so far.
I'm trying to find out how it is done. I need to run the tests outside Atom. I will read Atom source code in order to find out, but maybe some one already know that?
Another alternative I was thinking was to use Babel to translate to ES5 and then run the tests, but Atom way seems better.
Any ideas?
I'm trying to find the best way for debug gulp plugins during developing using webstorm. I have a project example and couple gulp plugins, and I want to trace and inspect the code in webstorm right after I run gulp command in terminal. Ideally I want to add debugger statement or breakpoint inside the webstorm to trace the code execution.
Use this guide (shameless self promotion) to setup your configurations. Then debug should just work as is.
Also, you won't need to run gulp from commandline separately, since webstorm will do that for you.
this is an old question, and has an very good answer,
here is another one with VS Code
debugging-gulp-in-VS-Code