-
Notifications
You must be signed in to change notification settings - Fork 0
Community: FAQ
A: The error-enhanced package extends the native JavaScript Error object, providing additional properties and methods for comprehensive error handling and reporting.
A: Use npm with the command: npm install @labrynx/error-enhanced. For more options, see the Installation Guide.
A: Absolutely! Start by opening an issue or a pull request on GitHub. Check out our Contributing Guidelines.
A: Yes, it provides strongly-typed interfaces for enhanced error objects.
A: Yes, the package is extensible. See the Enhancers section for more.
A: Use the Category enum. More details are in the Enums section.
A: We adhere to Semantic Versioning. See the Semantic Versioning page for more.
A: We use a combination of unit tests and end-to-end tests to ensure reliability. More details can be found in the Testing section.
A: Yes, the package is designed to be extensible, allowing integration with external logging and monitoring services.
A: Yes, you can extend the existing interfaces to add custom properties or methods as per your project's needs.
A: Use npm update @labrynx/error-enhanced. Make sure to check the Semantic Versioning page for breaking changes.
A: Please open a new issue on the GitHub repository. Make sure to follow the issue template for faster resolution.
A: The package provides a SerializersUtility class, which includes methods for error serialization. Check out the Utilities section for more.
A: The package is optimized for minimal performance impact but it's always good to profile and test in your specific use-case.
A: There are no inherent rate limits in the package itself, but always consider the limitations of any third-party services you integrate with.
A: Properties like _fileInfo, _lineNumber will have default values.
A: Use the fullStack getter.
A: An error will be thrown for invalid codes.
A: Yes, methods return this, allowing chaining.
A: Keys must be valid, non-empty strings.
A: An error will be thrown.
A: Yes, each generates a new unique ID.
A: An error will be thrown.
A: No, use refreshSystemInfo().
A: An error will be thrown.
A: Yes, it's designed to be flexible.
A: If it's null, undefined, an empty string, or -1.
A: Yes, 'name' and 'message' are always preserved.
A: No, it returns a new filtered object.
A: An error is logged, and an exception is thrown.
A: Yes, use the toJSON method with a custom replacer function.
error-enhanced Wiki
Version: 1.2.1 - © 2023
🔗 MIT License | 📦 GitHub Repository | 🐞 Report Issues | ✉️ Contact