.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,20 @@
+<!-- First of all, check the troubleshooting wiki page for common issues at:
+https://github.com/kulshekhar/ts-jest/wiki/Troubleshooting -->
+
+## Issue <!-- describe the issue below -->:
+
+
+## Expected behavior <!-- describe the expected behavior below -->:
+
+
+## Output from debug log <!-- You can activate the debug logger by setting the environment variable TS_JEST_DEBUG="true" before running yarn test. The output of the logger will be in **<your_project_dir>/node_modules/ts-jest/debug.txt**, paste it below -->:
+```bash
+# content of debug.txt :
+
+```
+
+
+## Minimal repo <!-- If you haven't already, create the smallest possible repo that reproduces this issue by running `npm install` and `npm test`. This will speed up any fixes that this issue might need. Paste the minimal repo URL below -->:
+
+
+<!-- Optional (but highly recommended): Configure Travis (or your favorite system) with the minimal repo. This allows potential solutions to be tested against the minimal repo. This saves everyone time and avoids a lot of back and forth. -->

.gitignore

@@ -43,3 +43,7 @@ jspm_packages
 
 .vscode
 .idea
+
+
+# Long paths
+tests/simple-long-path/long-src-path

.travis.yml

@@ -1,8 +1,11 @@
 dist: trusty
 sudo: required
 language: node_js
+cache: yarn
+git:
+  depth: 5
 node_js:
-  - "9"
+  - "10"
   - "8"
   - "6"
 before_install:

AUTHORS

@@ -3,38 +3,46 @@
 #
 #   Name/Organization <email address>
 
+Ahn Pham <anhpnnd@gmail.com>
+Alan Agius <alan.agius4@gmail.com>
 Alex Jover Morales <alexjovermorales@gmail.com>
 Andreas Krummsdorf <andreas.krummsdorf@doksafe.de>
 Anonymous <goodforonefare@gmail.com>
 Bartosz Gościński <bargosc@gmail.com>
 Blake Embrey <hello@blakeembrey.com>
+Bnaya Peretz <me@bnaya.net>
 Brian Ruddy <briancruddy@gmail.com>
 Chong Guo <cguo@azendless.com>
 Chris Sauve <chrismsauve@gmail.com>
 Christian Linne <ShadowVampire@web.de>
 Christian Rackerseder <git@echooff.de>
 Daniel Perez Alvarez <unindented@gmail.com>
+Danilo Bürger <info@danilobuerger.de>
 David Schkalee <david.schkalee@magicline.de>
 David Sheldrick <djsheldrick@gmail.com>
 Emil Persson <emil.n.persson@gmail.com>
 Eric Anderson <e@ericlanderson.com>
 Felipe Matos <felipems@yahoo.com.br>
 Forbes Lindesay <forbes@lindesay.co.uk>
 Gino Zhang <whitetrefoil@gmail.com>
+Gregor Stamac <1668205+gstamac@users.noreply.github.com>
 Gustav Wengel <gustavwengel@gmail.com>
 Henry Zektser <japhar81@gmail.com>
+Huafu Gandon <huafu.gandon@gmail.com>
 Ihor Chulinda <ichulinda@gmail.com>
 J Cheyo Jimenez <cheyo@masters3d.com>
 Jim Cummins <jimthedev@gmail.com>
 Joscha Feth <joscha@feth.com>
 Junle Li <lijunle@gmail.com>
 Justin Bay <jwbay@users.noreply.github.com>
+Kamijin Fanta <kamijin@live.jp>
 Kulshekhar Kabra <kulshekhar@users.noreply.github.com>
 Kyle Roach <kroach.work@gmail.com>
 Marshall Bowers <elliott.codes@gmail.com>
 Martijn The <post@martijnthe.nl>
 Matheus Gambati <matheusgambati@gmail.com>
 Maxim Samoilov <samoilowmaxim@gmail.com>
+Michael Tiller <michael.tiller@xogeny.com>
 Mohammad Rajabifard <mo.rajbi@gmail.com>
 OJ Kwon <kwon.ohjoong@gmail.com>
 Oliver Joseph Ash <oliverjash@gmail.com>
@@ -45,5 +53,6 @@ Rikki Tooley <rikki.tooley@travellocal.com>
 Simen Bekkhus <sbekkhus91@gmail.com>
 Thomas Fontaine <thomas.fontaine@me.com>
 Tom Crockett <tomcrockett@tuplehealth.com>
+Tony Valderrama <tony.valderrama@outlook.com>
 Trivikram Kamat <trivikr.dev@gmail.com>
 Umidbek Karimov <uma.karimov@gmail.com>

CHANGELOG.md

@@ -0,0 +1,3 @@
+#### All release changes can be seen in the release page
+
+Release page URL: https://github.com/kulshekhar/ts-jest/releases

COLLABORATORS.md

@@ -0,0 +1,60 @@
+<!-- START doctoc generated TOC please keep comment here to allow auto update -->
+<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
+**Table of Contents**
+
+- [Collaborator Guidelines](#collaborator-guidelines)
+  - [Installing and building the project](#installing-and-building-the-project)
+  - [Merging PRs](#merging-prs)
+  - [Versioning](#versioning)
+  - [Tests](#tests)
+    - [How to add tests](#how-to-add-tests)
+    - [How to run tests](#how-to-run-tests)
+
+<!-- END doctoc generated TOC please keep comment here to allow auto update -->
+
+# Collaborator Guidelines
+
+ts-jest is grateful for all issues, PRs and contributions. In this file are tips for getting started contributing,
+and best practices, so that we can ensure that we can maintain this project in the future.
+
+## Installing and building the project
+
+To be able to install and build the project probably, `rimraf` is required. Install `rimraf` by running
+```
+yarn global add rimraf
+```
+
+After installing `rimraf`, `yarn` command can be run normally when installing dependencies for the project
+
+## Merging PRs
+
+1. A PR should be merged when at least one of the following conditions is satisfied:
+
+- 2 collaborators have reviewed and okayed the PR
+- 1 collaborator has reviewed and okayed the PR and 36 hours have passed after the PR was submitted
+
+2. Collaborators should squash and merge PRs with a commit message explaining the changes.
+
+3. All PRs should add the author's name and email address to the authors file, if it isn't already present.
+
+## Versioning
+
+ts-jest must match the major version of jest. Matching the minor version is preferred. Matching the version patch is not required.
+
+When merging PRs which fix bugs, it is preferable to increment the version patch version so that the changes can be published to NPM.
+
+## Tests
+
+All new features or bugfixes should be accompanied with a new test, to ensure that the change works as intended, and to make sure we don't inadvertently break it in the future through refactring
+
+If you are simply refactoring code, it is not needed to add a test.
+
+### How to add tests
+- Tests are added by creating a new file in tests/__tests__ 
+- A test usually consists of two parts
+	 - A directory under tests/ that have some files that should result in a specific output when jest is passed through it
+	 - A file under tests/__tests__ that uses the runJest command to run Jest on the specified directory, and makes asserts on the output of stdout and stderr
+	 	When asserting things on the output, it is common to both assert something about the exit code, and something about the output. Always assert on the output first, before asserting on the status code - as it leads to much nicer error messages when refactoring. (You get the full output text, rather than just '0 didn't equal 1')
+
+### How to run tests
+Tests are run through `yarn test`