Skip to content
This repository has been archived by the owner on Mar 8, 2020. It is now read-only.

Update cache-loader to the latest version 馃殌 #172

Merged
merged 2 commits into from Apr 20, 2019

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Apr 19, 2019

The dependency cache-loader was updated from 2.0.1 to 3.0.0.

This version is not covered by your current version range.

If you don鈥檛 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 v3.0.0

Bug Fixes

Features

BREAKING CHANGES

  • default cache directory is node_modules/.cache/cache-loader
Commits

The new version differs by 8 commits.

  • 1369c05 chore(release): 3.0.0
  • 4924341 fix: usage with raw loaders (#69)
  • 74037ce chore: replace prepublish with prepare npm script (#66)
  • 52a4a4f chore: audit and fix dependencies (#67)
  • fd1c6d7 feat: change default cache directory (#64)
  • 0eae4e6 chore: audit fix deps (#65)
  • 4fb8478 Read only option (#61)
  • e764087 docs: fix broken tests badge in README (#60)

See the full diff

FAQ and help

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


Your Greenkeeper bot 馃尨

@coveralls
Copy link

Pull Request Test Coverage Report for Build 751

  • 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 93.865%

Totals Coverage Status
Change from base Build 748: 0.0%
Covered Lines: 103
Relevant Lines: 104

馃挍 - Coveralls

@brunocodutra brunocodutra merged commit 3eafd87 into master Apr 20, 2019
@greenkeeper greenkeeper bot deleted the greenkeeper/cache-loader-3.0.0 branch April 20, 2019 11:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants