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

node_modules folder significantly slow down the scan process #899

Open
ghozylab opened this issue Mar 27, 2025 · 5 comments
Open

node_modules folder significantly slow down the scan process #899

ghozylab opened this issue Mar 27, 2025 · 5 comments
Assignees

Comments

@ghozylab
Copy link

Hi All,

I am using Plugin Check (PCP) and not using WP-CLI but using WordPress admin interface, In this case my node_modules folder inside the plugin folder so it significantly slow down the scan process.
The scan process can takes more than 3 minutes when the node_modules folder (and all its packages) exist inside plugin directory. Can I ignore the node_modules folder? Thanks

@ghozylab ghozylab changed the title node_modules significantly slow down the scan process node_modules folder significantly slow down the scan process Mar 27, 2025
@davidperezgar davidperezgar self-assigned this Mar 27, 2025
@davidperezgar
Copy link
Member

I'll check it out!

@ernilambar
Copy link
Member

ernilambar commented Mar 28, 2025

By default following folders in the plugin are ignored.

$default_ignore_directories = array(
        '.git',
        'vendor',
        'node_modules',
);

It is quite strange that PCP is checking node_modules folder in your case.

@ghozylab
Copy link
Author

You can try to install the following package to make it same with mine and check again to scan PCP.

{ "name": "new-package", "version": "1.0.0", "main": "index.js", "scripts": { "start": "webpack serve --config webpack.config.js --open", "build": "webpack --config webpack.config.js --mode production", "watch": "webpack --watch --config webpack.config.js --mode development", "dev": "webpack serve --config webpack.config.js --mode development --open" }, "author": "", "license": "ISC", "devDependencies": { "autoprefixer": "^10.4.20", "babel-loader": "^10.0.0", "clean-webpack-plugin": "^4.0.0", "css-loader": "^6.8.1", "css-minimizer-webpack-plugin": "^5.0.1", "dotenv": "^16.3.1", "file-loader": "^6.2.0", "filemanager-webpack-plugin": "^8.0.0", "glob": "^11.0.1", "html-webpack-plugin": "^5.5.3", "htmlhint": "^1.1.4", "ignore-emit-webpack-plugin": "^2.0.6", "mini-css-extract-plugin": "^2.7.6", "postcss": "^8.5.3", "postcss-loader": "^8.1.1", "rimraf": "^6.0.1", "style-loader": "^3.3.3", "tailwindcss": "^3.3.2", "terser-webpack-plugin": "^5.3.9", "webpack": "^5.98.0", "webpack-cli": "^5.1.4", "webpack-dev-server": "^4.15.1" }, "dependencies": { "@simonwep/pickr": "^1.9.1", "@wordpress/block-editor": "^14.14.0", "@wordpress/blocks": "^14.8.0", "@wordpress/components": "^29.5.0", "@wordpress/element": "^6.19.0", "@wordpress/i18n": "^5.19.0", "@wordpress/scripts": "^30.12.0", "antd": "^5.24.3", "jquery": "^3.7.1", "jquery-contextmenu": "^2.9.2", "jquery-toast-plugin": "^1.3.2", "jquery.scrollto": "^2.1.3", "react": "^18.2.0", "react-dom": "^18.2.0", "simplebar": "^6.2.5", "tippy.js": "^6.3.7" }, "resolutions": { "react": "18.2.0", "react-dom": "18.2.0" }, "keywords": [], "description": "" }

@ernilambar
Copy link
Member

I tried with above package.json but could not reproduce the error.

@ghozylab
Copy link
Author

ghozylab commented Apr 5, 2025

Yes, its not reproduce the error, but the scan process very very slow

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

No branches or pull requests

3 participants