Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / expressjs/errorhandler issues and pull requests

#27 - chore: add support for OSSF scorecard reporting

Pull Request - State: closed - Opened by inigomarquinez about 1 month ago

#26 - Update var to const

Pull Request - State: closed - Opened by hasantezcan about 4 years ago - 2 comments
Labels: docs, pr

#25 - 'errorhandler@^1.5.0' is not in the npm registry

Issue - State: closed - Opened by sandupa-govinena over 4 years ago - 2 comments

#24 - No matching version found for errorhandler@^1.5.1

Issue - State: closed - Opened by levitomer over 4 years ago - 4 comments

#23 - Allow to change output structor

Issue - State: closed - Opened by wxs77577 about 5 years ago - 3 comments

#22 - Latest versions of Node.js added to Travis config

Pull Request - State: closed - Opened by ppitonak over 7 years ago
Labels: pr

#21 - Travis config updated to contain latest supported versions of Node.js

Pull Request - State: closed - Opened by ppitonak over 7 years ago - 3 comments
Labels: pr

#20 - The options object accepts a property 'title'

Pull Request - State: closed - Opened by Tarabass about 8 years ago - 1 comment
Labels: pr

#19 - errorhandler with express

Pull Request - State: closed - Opened by Knighton910 over 8 years ago - 4 comments
Labels: docs, pr

#18 - express with errorhandler module

Pull Request - State: closed - Opened by Knighton910 over 8 years ago - 6 comments
Labels: docs, pr

#17 - link to errorhandling docs

Pull Request - State: closed - Opened by Knighton910 over 8 years ago - 9 comments
Labels: docs, pr

#16 - Can't get errorhandler to work in Express 4

Issue - State: closed - Opened by rawaludin over 8 years ago - 7 comments
Labels: question

#15 - Typo

Pull Request - State: closed - Opened by cilindrox over 8 years ago - 2 comments
Labels: docs, pr

#14 - More readable output formats

Issue - State: closed - Opened by rightaway over 8 years ago - 1 comment
Labels: question

#13 - Proposal: suppress stack traces in HTTP responses when running in production

Issue - State: closed - Opened by bajtos almost 9 years ago - 13 comments
Labels: discuss

#12 - support reading statusCode from err.statusCode

Pull Request - State: closed - Opened by yorkie about 9 years ago - 2 comments
Labels: enhancement, pr

#11 - read statusCode from err.statusCode?

Issue - State: closed - Opened by yorkie about 9 years ago - 5 comments
Labels: enhancement

#10 - Whole stack trace is outputted in the headline

Pull Request - State: closed - Opened by oblador over 9 years ago - 8 comments
Labels: bug, pr

#9 - Provide option to specify a log callback instead of using console.error

Pull Request - State: closed - Opened by myndzi over 9 years ago - 17 comments
Labels: enhancement, pr

#8 - issue #7 - use util.inspect instead of String()

Pull Request - State: closed - Opened by alexbeletsky almost 10 years ago - 4 comments
Labels: enhancement, pr

#7 - Use util.inspect for logging errors

Issue - State: closed - Opened by alexbeletsky almost 10 years ago - 6 comments
Labels: enhancement, investigate

#6 - Please clarify copyright

Issue - State: closed - Opened by LeoIannacone almost 10 years ago - 2 comments

#5 - Nothing displayed when error doesn't contain a .stack

Issue - State: closed - Opened by dantman about 10 years ago - 3 comments
Labels: bug

#4 - setting status code

Issue - State: closed - Opened by sprzybylski about 10 years ago - 5 comments
Labels: invalid

#3 - Fix code error in README

Pull Request - State: closed - Opened by EvanHahn about 10 years ago - 1 comment

#2 - missing semicolon in README.md usage

Issue - State: closed - Opened by srl295 about 10 years ago - 2 comments
Labels: question, wontfix

#1 - remove directory CSS

Issue - State: closed - Opened by jonathanong over 10 years ago