Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / sindresorhus/aggregate-error issues and pull requests
#22 - Update clean-stack dependency to latest version
Issue -
State: closed - Opened by clibu about 1 year ago
#21 - Thoughts on requiring Node 14?
Issue -
State: closed - Opened by manzt over 1 year ago
- 2 comments
#20 - support es5 syntax
Issue -
State: closed - Opened by arvinxx over 2 years ago
- 1 comment
#19 - Handles empty stack strings.
Pull Request -
State: closed - Opened by tommie over 2 years ago
#18 - Use native AggregateError if available
Issue -
State: closed - Opened by mk-pmb over 2 years ago
- 1 comment
#17 - low level browsers do not support private-methods
Issue -
State: closed - Opened by bplok20010 over 3 years ago
- 1 comment
#16 - Move to GitHub Actions
Pull Request -
State: closed - Opened by Richienb almost 4 years ago
#15 - Remove redundant array cloning
Pull Request -
State: closed - Opened by riophae about 4 years ago
#14 - question[TypeScript] How should AggregateError be imported as type when using TypeScript without esModuleInterop option
Issue -
State: closed - Opened by oscard0m about 4 years ago
- 5 comments
#13 - Support custom `Error` subclass in the TypeScript types
Pull Request -
State: closed - Opened by gr2m over 4 years ago
- 1 comment
#12 - Add message argument
Issue -
State: open - Opened by CxRes over 4 years ago
- 1 comment
Labels: enhancement, help wanted
#11 - Optionally flatten nested AggregateErrors
Pull Request -
State: closed - Opened by argv-minus-one over 5 years ago
- 3 comments
#10 - Change AggregateError constructor to accept any iterable, not just an array
Pull Request -
State: closed - Opened by argv-minus-one over 5 years ago
- 3 comments
#9 - Refactor TypeScript definition to CommonJS compatible export
Pull Request -
State: closed - Opened by BendingBender over 5 years ago
#8 - Add TypeScript definition
Pull Request -
State: closed - Opened by BendingBender over 5 years ago
#7 - Gracefully handle `Error` instances without a `stack` property
Pull Request -
State: closed - Opened by kmohrf almost 6 years ago
- 3 comments
#6 - message generation breaks when AbortError/Error without stack is encountered
Issue -
State: closed - Opened by kmohrf almost 6 years ago
- 4 comments
Labels: bug, help wanted
#4 - Make it more spec compliant
Issue -
State: open - Opened by BebeSparkelSparkel almost 7 years ago
- 15 comments
Labels: enhancement, help wanted
#3 - Support plain objects
Pull Request -
State: closed - Opened by felixfbecker almost 7 years ago
- 8 comments
#2 - Tests are failing on master
Issue -
State: closed - Opened by felixfbecker almost 7 years ago
- 2 comments
#1 - Handling errors without stacks
Issue -
State: closed - Opened by SEAPUNK about 8 years ago
- 2 comments