https://github.com/techeng322/file-debugger-nodejs

A mock for PrismaClient, dedicated to unit testing.
https://github.com/techeng322/file-debugger-nodejs

Last synced: 18 days ago
JSON representation

A mock for PrismaClient, dedicated to unit testing.

• Host: GitHub
• URL: https://github.com/techeng322/file-debugger-nodejs
• Owner: techeng322
• Created: 2023-11-08T19:54:13.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2023-12-03T21:54:13.000Z (about 1 year ago)
• Last Synced: 2024-01-15T10:34:57.929Z (about 1 year ago)
• Language: JavaScript
• Homepage: https://www.npmjs.com/package/prismock
• Size: 887 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# File Debugger

## Introduction

Debugs files being accessed by any NodeJS dependency.

- Adds automatic breakpoint at the line where the file is being read

- Logs all the files that are being read

## Motivation

- Sometimes you add/change something in a config file and expect an npm dependency to act on it, but what if it does't work. How do you know where, how and in which condition that dependency accesses that file.

## Usage

Global Installation - Recommended, so that you install it once and can use it in all your projects

`npm i file-debugger -g`

Run script with a require of `file-debugger`

`node -r file-debugger your_file_with_hundreds_of_deps.js`

Optionally you can install locally but you would have to repeat it for every project

`npm i file-debugger --save-dev`

### Configuration using environment variables

Enable Logging using `FILE_DEBUGGER_DEBUG_LOG="1"`



Enable automatic debugger using `FILE_DEBUGGER_TRACE_THIS="SUBSTRING_MATCHING_FILE_PATH_NAME"`