<commit_before>Nested stacktraces for Node.js!
===============================

[![Build Status](https://github.com/mdlavin/nested-error-stacks/actions/workflows/test.yml/badge.svg)](https://github.com/mdlavin/nested-error-stacks/actions?query=branch%3Amaster)
[![NPM version](https://badge.fury.io/js/nested-error-stacks.svg)](http://badge.fury.io/js/nested-error-stacks)

With this module, you can wrap a caught exception with extra context
for better debugging.  For example, a network error's stack would normally look
like this:
<commit_msg>Fix build badge image<commit_after>Nested stacktraces for Node.js!
===============================

[![Build Status](https://github.com/mdlavin/nested-error-stacks/actions/workflows/test.yaml/badge.svg)](https://github.com/mdlavin/nested-error-stacks/actions?query=branch%3Amaster)
[![NPM version](https://badge.fury.io/js/nested-error-stacks.svg)](http://badge.fury.io/js/nested-error-stacks)

With this module, you can wrap a caught exception with extra context
for better debugging.  For example, a network error's stack would normally look
like this:

{'fraction_non_alphanumeric': 0.18891916439600362, 'fraction_numerical': 0.0018165304268846503, 'mean_word_length': 5.8875, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3122619', 'n_tokens_mistral': 358, 'n_tokens_neox': 345, 'n_words': 71}