Contributing to JS Recon Tool
Reporting Bugs
If you find an issue with the tool, please create a new issue on GitHub here.
Requesting new support for new technologies
If the tool doesn't support a framework and you want the tool to support it, please create a new issue on GitHub here.
Contributing to the codebase
Setting the dev environment
First of all, clone the repository:
git clone https://github.com/shriyanss/js-recon.git
cd js-recon
npm install
The tool supports Node.js v22.17.0 (LTS) or later with npm as the package manager. You can download it from here.
How the codebase is structured
First of all, these three npm scripts would be helpful:
npm run build # build the tool
npm run start # run the tool in production mode
npm run cleanup # remove all the output files of tool and build the tool again
All the code for this tool is written in TypeScript, and is under the src/
directory. The file index.ts
is the entry point of the tool. It contains all the CLI arguments for the tool, and executes the responsible functions.
The code for the modules is stored in directories inside the src/
directory, except for the utility
directory.
The directories for the modules contain a file index.ts
, which is the entry point for the module.
Making a Pull Request
- Fork the repo
- Create a new branch from the
dev
branch
git checkout -b <your-feature-name> dev
- Commit your changes with meaningful commit messages
git add <files>
git commit -m "[feat/chore/fix/docs]: <meaningful commit message>"
- Push your branch
git push origin <your-feature-name>
-
Open a pull request to the
dev
branch -
When the PR is created, make sure that all the checks pass. If any of the checks fail, fix the issues and push the changes again.
-
Once all the tests pass, the changes will be reviewed by the maintainers. If the changes are accepted, they will be merged into the
dev
branch. -
The changes will be available in the next release of the tool.
-
If you want to contribute to the docs, please create a new pull request on GitHub here.