search

katallaxie / vue-preboot

:neckbeard: A teeny Vue.js + TypeScript boilerplate with SSR :thumbsup:. It is opinionated and powered by Webpack.
MIT License
9 stars 0 forks source link

An in-range update of css-loader is breaking the build 🚨 #119

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency css-loader was updated from 2.1.0 to 2.1.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

css-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/katallaxie/vue-preboot/builds/503029963?utm_source=github_status&utm_medium=notification)).
Release Notes for v2.1.1

2.1.1 (2019-03-07)

Bug Fixes

  • do not break selector with escaping (#896) (0ba8c66)
  • source map generation when sourceRoot is present (#901) (e9ce745)
  • sourcemap generating when previous loader pass sourcemap as string (#905) (3797e4d)
Commits

The new version differs by 13 commits.

  • bc16c3d chore(release): 2.1.1
  • b671db7 fix: don't remove value from attribute selector (#904)
  • 3797e4d fix: sourcemap generating when previous loader pass sourcemap as string (#905)
  • cc81af1 refactor: stuff (#903)
  • e9ce745 fix: source map generation when sourceRoot is present (#901)
  • a49e904 docs: improve documentation for hashPrefix, context, getLocalIdent (#900)
  • c309788 refactor: avoid lodash in favor native implementations
  • 0ba8c66 fix: do not break selector with escaping (#896)
  • 2293eb0 chore: update defaults (#895)
  • 2a2ee7b docs: sourceMaps are disabled by default (#890)
  • 2d45e95 test: base64 (#888)
  • 1fb8948 docs: update README.md (#885)
  • 034f9a3 test: emoji (#881)

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

After pinning to 2.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.