Skip to content

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

ts-node just published its new version 2.0.0.

State Update 🚀
Dependency ts-node
New version 2.0.0
Type devDependency

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

  • Requires node.js v4 or greater
  • Use module._preloadModules to handle --require
  • Use new Script over the deprecated createScript method

The new version differs by 13 commits .

  • 9409899 v2.0.0
  • 5623aff Use new Script for node > v4 (#256)
  • 50df9b1 Fix preloading of modules (#258)
  • b2e6990 v1.7.3
  • bcc1ff4 Pass through --preserve-symlinks flag (#253)
  • 42e5c19 Add more info about programmatic usage (#251)
  • 55be95c v1.7.2
  • e760502 Improve handling of the REPL for ASI and modules
  • dd15f7f v1.7.1
  • eb2f9a4 Do not delete the stack from TSError
  • 67e2981 Update to TypeScript 2.1
  • aa07292 Update TSLint
  • c4d3e8a chore(package): update typings to version 2.0.0 (#236)

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@coveralls
Copy link

coveralls commented Dec 29, 2016

Coverage Status

Coverage remained the same at 99.507% when pulling aed51bd413755f67f19367c512ea01b75a86876c on greenkeeper-ts-node-2.0.0 into a6a3ad3 on master.

@mseemann mseemann force-pushed the greenkeeper-ts-node-2.0.0 branch from aed51bd to 6ef89ac Compare February 28, 2017 07:59
@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.507% when pulling 6ef89accb46a0a1ed58b23b59030cd83392855e8 on greenkeeper-ts-node-2.0.0 into 8e15bb8 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.507% when pulling 6ef89accb46a0a1ed58b23b59030cd83392855e8 on greenkeeper-ts-node-2.0.0 into 8e15bb8 on master.

@mseemann mseemann force-pushed the greenkeeper-ts-node-2.0.0 branch from 6ef89ac to 70719aa Compare March 11, 2017 15:32
@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.507% when pulling 70719aa on greenkeeper-ts-node-2.0.0 into 656bc0e on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.507% when pulling 70719aa on greenkeeper-ts-node-2.0.0 into 656bc0e on master.

@mseemann mseemann merged commit 958ce61 into master Mar 11, 2017
@mseemann mseemann deleted the greenkeeper-ts-node-2.0.0 branch March 11, 2017 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants