node-async-stacktrace 0.0.2-6 source package in Ubuntu
Changelog
node-async-stacktrace (0.0.2-6) unstable; urgency=medium * Team upload [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Update standards version to 4.5.1, no changes needed. [ Yadd ] * Update standards version to 4.6.0, no changes needed. * Add "Rules-Requires-Root: no" * Modernize debian/watch * Fix filenamemangle * Fix GitHub tags regex * Use dh-sequence-nodejs instead of pkg-js-tools * Drop dependency to nodejs -- Yadd <email address hidden> Sun, 02 Jan 2022 18:52:26 +0100
Upload details
- Uploaded by:
- Debian Javascript Maintainers
- Uploaded to:
- Sid
- Original maintainer:
- Debian Javascript Maintainers
- Architectures:
- all
- Section:
- javascript
- Urgency:
- Medium Urgency
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
node-async-stacktrace_0.0.2-6.dsc | 2.1 KiB | f9ce059fa5b96d125481d159401f4b8465a20bd7bc99ec6dacc53c982f7ee9e8 |
node-async-stacktrace_0.0.2.orig.tar.gz | 2.9 KiB | 019576ec27acd0836f48a6a5b2e2729bc1c27ba34e21795dffc79fc3dad88c05 |
node-async-stacktrace_0.0.2-6.debian.tar.xz | 3.0 KiB | 0eb716328b1283cefee678dd260aeadbe3f3cf6724f133ad3b310abbfc2e9ad9 |
Available diffs
- diff from 0.0.2-5 to 0.0.2-6 (1.1 KiB)
No changes file available.
Binary packages built by this source
- node-async-stacktrace: Improve Node.js stacktraces and make it easier to handle errors
The "Async Stacktrace" module eases debugging of Node.js applications. With the
default stacktraces, the problem is that they do not tell you exactly where
a problematic subroutine has been called from.
.
The "Async Stacktrace" module shows you where an error was caught and passed to
the next callback. This allows you to see from where problematic code was
called.