Skip to content

Update ts-loader to version 2.0.1 🚀 #60

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.

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

Closed
wants to merge 1 commit into from

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

ts-loader just published its new version 2.0.1.

State Update 🚀
Dependency ts-loader
New version 2.0.1
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-loader.
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


The new version differs by 42 commits .

There are 42 commits in total. See the full diff.


✨ Try the all new Greenkeeper GitHub Integration
With Integrations first-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.

Screencast

Try it today. Free for private repositories during beta.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f2c784a on greenkeeper-ts-loader-2.0.1 into 4f642ac on master.

@mseemann mseemann force-pushed the greenkeeper-ts-loader-2.0.1 branch from f2c784a to d500eed Compare February 28, 2017 07:59
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling d500eed on greenkeeper-ts-loader-2.0.1 into 468db3f on master.

@mseemann mseemann force-pushed the greenkeeper-ts-loader-2.0.1 branch 2 times, most recently from 0db22b2 to d0cb34d Compare March 2, 2017 09:31
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling d0cb34d on greenkeeper-ts-loader-2.0.1 into 4b71c85 on master.

@mseemann mseemann force-pushed the greenkeeper-ts-loader-2.0.1 branch from d0cb34d to cf62cff Compare March 10, 2017 06:37
@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.696% when pulling cf62cff on greenkeeper-ts-loader-2.0.1 into 49b16e9 on master.

@mseemann mseemann force-pushed the greenkeeper-ts-loader-2.0.1 branch from cf62cff to 1751fe2 Compare March 10, 2017 09:53
@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.696% when pulling 1751fe2 on greenkeeper-ts-loader-2.0.1 into be1075d on master.

@mseemann mseemann force-pushed the greenkeeper-ts-loader-2.0.1 branch from 1751fe2 to b970c5c Compare March 10, 2017 14:54
@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.696% when pulling b970c5c on greenkeeper-ts-loader-2.0.1 into 59c0355 on master.

@mseemann mseemann closed this Mar 10, 2017
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