Zipy CLI helps in debugging the minified stack trace that occurs on the user's browser environment. The minified stack trace can be parsed, so that you can see the actual source code with the help of source maps. This lets you view the actual source context of the frontend JavaScript errors, including the code from any other libraries that you may have used in your frontend code.

How to enable this feature?
You will have to upload the source maps to Zipy Server with the help of the CLI. The package can be globally installed and integrated in the build steps for smoother integration. Following are the steps to upload the source map files:

// Globally install the cli package -
npm i -g zipy-cli

// CLI Command -
zipy-cli --username username --password password --dirname ~/sourcemaps/ --apiKey zipyProjectKey --releaseVer releaseVerString

// CLI help command -
zipy-test-cli --help

Below are the params accepted by the CLI:

  • username
  • password
  • dirname: A string value of the directory where source maps are available
  • apiKey: Zipy Project Key
  • releaseVer: Release Version of your application

Please contact Zipy at to get the credentials for access. Note that you can upload only up to 100 files at once.

Why can't I see the proper stack trace?

If you are unable to see the proper stack trace in your Zipy dev tools section, please verify the following:

1. Check if you initialized the SDK with a proper release version. Make sure the release version for which the sourcemaps have been uploaded matches with SDK init release version.

2. Confirm if you uploaded all the source map files. Stack traces can be broken if some souce map files are missing.