Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G gulp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gulp
  • gulp
  • Merge requests
  • !1567

Log require fail reason

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Administrator requested to merge github/fork/blakeembrey/emit-require-fail-reason into master Mar 17, 2016
  • Overview 8
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: blakeembrey

Currently, requiring modules like ts-node/register can fail for unrelated issues (invalid tsconfig.json, no typescript installed, etc). It would be helpful for debugging to log out the reason it failed.

Related to https://github.com/TypeStrong/ts-node/issues/26.

It is possible to change the error level to error.stack instead, but the message is probably enough most of the time. Also, it may make sense to log it as part of the same log message - not sure what the etiquette is there.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/blakeembrey/emit-require-fail-reason