Update ts-node to version 2.1.0 🚀 #30
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Coverage remained the same at 99.507% when pulling 7caad967cacf88c7247fb473152dd80d6fe6b153 on greenkeeper-ts-node-2.1.0 into a6a3ad3 on master. |
1 similar comment
|
Coverage remained the same at 99.507% when pulling 7caad967cacf88c7247fb473152dd80d6fe6b153 on greenkeeper-ts-node-2.1.0 into a6a3ad3 on master. |
mseemann
force-pushed
the
greenkeeper-ts-node-2.1.0
branch
from
7caad96 to
e695e06
Compare
|
Coverage remained the same at 99.507% when pulling e695e06ec9443fac7b9a12a41f62a54189b5790f on greenkeeper-ts-node-2.1.0 into 8e15bb8 on master. |
1 similar comment
|
Coverage remained the same at 99.507% when pulling e695e06ec9443fac7b9a12a41f62a54189b5790f on greenkeeper-ts-node-2.1.0 into 8e15bb8 on master. |
mseemann
force-pushed
the
greenkeeper-ts-node-2.1.0
branch
from
e695e06 to
3ad63d3
Compare
1 similar comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
ts-node just published its new version 2.1.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ts-node.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
Changed
The new version differs by 17 commits .
01fbfcev2.1.0da065efUseos.homedirto calculatetmpdir(#267)1ed4d6fchore(package): update tslint-config-standard to version 3.0.0 (#265)ee1e1e1Fixed a typo in README example (#260)9409899v2.0.05623affUsenew Scriptfor node > v4 (#256)50df9b1Fix preloading of modules (#258)b2e6990v1.7.3bcc1ff4Pass through--preserve-symlinksflag (#253)42e5c19Add more info about programmatic usage (#251)55be95cv1.7.2e760502Improve handling of the REPL for ASI and modulesdd15f7fv1.7.1eb2f9a4Do not delete the stack fromTSError67e2981Update to TypeScript 2.1There are 17 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.