Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update ts-node to the latest version 🚀 #10

Closed
wants to merge 2 commits into from
Closed

Update ts-node to the latest version 🚀 #10

wants to merge 2 commits into from

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Mar 7, 2019

The devDependency ts-node was updated from 7.0.1 to 8.0.3.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

Release Notes for Relative TypeScript

Added

  • Fall back on resolving relative TypeScript packages (normal resolution is from working directory, these two things can be the same in the case of locally installed packages)
Commits

The new version differs by 36 commits.

  • 8706c31 8.0.3
  • d065dd2 Update README note about relative installations
  • 655c43b Fallback on resolving TypeScript relatively (#793)
  • c2ecc7d Add note about local TypeScript to README (#789)
  • 7414752 Update README with triple-slash directive example (#776)
  • efaf67a Add VS Code env note to README (#738)
  • 2609663 Avoid incrementing memory cache unnecessarily
  • b4bdb08 Specify sensitive file names for document registry
  • c215693 Utilize TypeScript sys better for service host
  • 062254f Conditionally enable .[tj]sx extensions
  • 7f5284c 8.0.2
  • e009d79 Correct fixConfig include files
  • 7213c0f Use latest typescript for development
  • c8ddd66 Remove obsolete cache options in README (#767)
  • 544851e Remove globally installed typescript from README

There are 36 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper bot 🌴

@coveralls
Copy link

coveralls commented Mar 7, 2019 •
edited
Loading

Pull Request Test Coverage Report for Build 161

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 61.111%
Totals Coverage Status
Change from base Build 109: 0.0%
Covered Lines: 24
Relevant Lines: 40
💛 - Coveralls

brandondoran added a commit that referenced this pull request Mar 31, 2019
@brandondoran
Upgrade all packages to latest
13a38be 
This closes #7, closes #8, closes #9, closes #10, closes #11
@brandondoran brandondoran mentioned this pull request Mar 31, 2019
Merged
brandondoran added a commit that referenced this pull request Mar 31, 2019
@brandondoran
fix(package): upgrade all packages to latest (#12)
6878818 
Also includes package updates to the examples.

This closes #7, closes #8, closes #9, closes #10, closes #11
brandondoran pushed a commit that referenced this pull request Mar 31, 2019
@semantic-release-bot
chore(release): 1.1.2 [skip ci]
66796c2 
## [1.1.2](v1.1.1...v1.1.2) (2019-03-31)

### Bug Fixes

* **package:** upgrade all packages to latest ([#12](#12)) ([6878818](6878818)), closes [#7](#7) [#8](#8) [#9](#9) [#10](#10) [#11](#11)
@brandondoran
Copy link
Owner

🎉 This issue has been resolved in version 1.1.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@brandondoran brandondoran deleted the greenkeeper/ts-node-8.0.3 branch March 31, 2019 23:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
greenkeeper released
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@coveralls @brandondoran