JSPM

  • Created
  • Published
  • Downloads 3
  • Score
    100M100P100Q122224F
  • License MIT

Trace your code with ease

Package Exports

  • @racgoo/scry

Readme

πŸ” Scry

JavaScript/TypeScript execution flow tracking debugging tools

Version License PRs Welcome
Scry

Github: https://github.com/racgoo/scry

NPM: https://www.npmjs.com/package/@racgoo/scry


Introduction

Scry is a JavaScript and TypeScript function execution context tracing library that records every function and method callβ€”along with its name, input, and output.

It was created to ease the pain of debugging unexpected runtime errors and unhelpful error messages. Scry helps you clearly understand complex code flow and analyze relationships between function calls with precision.


Supports

Runtime Environments

  • Node.js - Server-side JavaScript runtime
  • Browser - Modern web browsers with ES2018+ support

Module Systems

  • CommonJS (CJS) - Traditional Node.js module system using require() and module.exports
  • ES Modules (ESM) - Modern JavaScript module system using import and export

Dual Package Support

  • This library provides dual package distribution with automatic module resolution:

Features

  • Full recording of function and method calls, including input and output values

  • Automatic tracking of function names and call stacks

  • Compatible with Node.js and browser environments. In the Browser, trace results are displayed directly in the console with a clickable link to view them in a new tab. In Node.js, results are saved as a current-trace.html file in the scry folder at the project root, which you can open in a browser to view the trace.


Trace Output & Report View

  • Browser

    Automatically opens the trace result page in a new browser tab when tracing is complete.

  • Node.js

    Saves the trace result as scry/current-trace.html at the project root β€” open it manually in a browser to view.

  • Report (WebUI)

스크란샷 2025-05-31 α„‹α…©α„Œα…₯ᆫ 12 42 51 스크란샷 2025-05-31 α„‹α…©α„Œα…₯ᆫ 12 43 17

Install

# use npm
npm i @racgoo/scry

# use yarn
yarn add @racgoo/scry

Usage

1. Babel Plugin Setting

Add the following plugin to your babel.config.js or .babelrc file

import { scryBabelPlugin } from "@racgoo/scry";
⚠️ Plugin setup may differ depending on the bundler you're using. ⚠️
If setting things up feels difficult, please refer to the "examples" in the GitHub repository.

----------------------------------------------------------------------
#vite example (vite.config.js)

!! ESM and CJS have identical execution behavior when using bundlers like Vite,
with the module system determined by package.json type configuration ("module" or "commonjs").
import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import { scryBabelPlugin } from "@racgoo/scry";

export default defineConfig({
  resolve: {
    preserveSymlinks: true,
  },
  plugins: [
    react({
      babel: {
        plugins: [scryBabelPlugin],
      },
    }),
  ],
});

----------------------------------------------------------------------
#nodejs example (babel.config.js)

1. ESM module system.(package.json.type === "module")
import { scryBabelPlugin } from "@racgoo/scry"; 
export default {
  presets: [],
  plugins: [scryBabelPlugin],
};

2. CJS module system.(package.json.type === "commonjs")
const { scryBabelPlugin } = require("@racgoo/scry");
module.exports = {
  presets: [],
  plugins: [scryBabelPlugin],
};

2. Execution Context Tracing

All function and method calls executed between Tracer.start() and Tracer.end() will have their names, input values, and return values automatically logged and recorded.

⚠️ Only works when NODE_ENV=development is set in your Node.js environment. ⚠️

import { Tracer } from "@racgoo/scry";

function foo(x: number) {
  return x * 2;
}

function bar(y: number) {
  return foo(y) + 1;
}

Tracer.start();
bar(5);
Tracer.end();

✨ Files inside node_modules are not traced. If you need this feature, feel free to contact us. ✨


πŸ”§ Future Work

Enhanced Parameter & Return Type Tracking

Further improvements are underway to better validate and track function parameters and return values, especially for complex nodes such as BinaryExpression, CallExpression, and others.

Async Function Support(~ing. comming soon:)

Tracing for asynchronous functions is not yet implemented. Development is currently in progress.

Improved error messaging

error handling and clearer error messages are currently under development.πŸ˜…


Contact

Have questions, suggestions, or want to contribute?
Feel free to reach out at

[πŸ“¬ send mail]