The hibari from wopian

Chrome	Firefox	Safari	Edge
61 and newer	55 and newer	10.1 and newer	15 and newer

An in-range update of vue-server-renderer is breaking the build 🚨

Version 2.3.3 of vue-server-renderer just got published.

Branch	Build failing 🚨
Dependency	vue-server-renderer
Current Version	2.3.2
Type	devDependency

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

As vue-server-renderer is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details,- ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v2.3.3

Fixed

#5586 fix unecessary input trigger with v-model on change event (@posva via #5589)
#5591 ssr template interpolation should be whitespace-insensitive (@HerringtonDarkholme via ##5597)
#5592 fix regression where text nodes are merged into comment placeholder nodes (@maggiehe via #5593)
#5610 fix Vue.use not chainable when plugin has already been installed, also makes Vue.mixin chainable. (@lzxb via #5610)
#5615 fix scoped slots when used together with v-for
#5618 fix slot elements after v-for being unnecessarily recreated (@gebilaoxiong via #5627)
#5633 fix comment nodes not cloned properly (@pengchongfu via #5633)
#5635 fix async components timeout triggered when already resolved

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Feed: Following Feed

An in-range update of vue-server-renderer is breaking the build 🚨

Version 2.3.1 of vue-server-renderer just got published.

Branch	Build failing 🚨
Dependency	vue-server-renderer
Current Version	2.3.0
Type	devDependency

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

As vue-server-renderer is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/wopian/hibari/builds/227873957?utm_source=github_status&utm_medium=notification),- ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/wopian/hibari/build/490)

Release Notes

v2.3.1

Fixed

#5536 fix regression when render function returns null (@gebilaoxiong via #5539)
#5540 vue-server-renderer/server-plugin: ensure assets are unique (@pi0 via #5540)
#5553 vue-server-renderer/server-plugin: avoid swallowing webpack error when entry is not found
#5559 vue-server-renderer: with runInNewContext: false, the bundle is now indeed executed in the same context. The 2.3.0 behavior is still available behind a new option value runInNewContext: 'once'. See docs for more details.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue is breaking the build 🚨

Version 2.2.6 of vue just got published.

Branch	Build failing 🚨
Dependency	vue
Current Version	2.2.5
Type	dependency

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

As vue is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.2.6

Fixed

Fixed a memory leak issue when used with vue-router (vuejs/vue-router#1279)
#5265 Warn when no getter is provided to a computed property (@kmc059000 via #5267)

Commits

The new version differs by 6 commits .

0cebdf5 [release] 2.2.6
113fce9 [build] 2.2.6
6fcfdbd warn and handle missing get in computed (fix #5265) (#5267)
3209f6f remove parent/ref elm references when destroying instance, fix memory leak (fix vue-router#1279)
be07617 fix a typo (#5284)
8a518c1 update sponsors and backers

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

User: Profile

Rogue character in anime favourites

Anime favourites of FullmetalHagane includes a rogue character in the anime favourites tab. Same character appears fine in character tab. This was previously breaking the page for this user before #83.

The favourites linker log dump shows that the character is combined with the correct anime favourite:

{
      "0": {
        "id": "2",
        "type": "characters",
        "links": {
          "self": "https://kitsu.io/api/edge/characters/2"
        },
        "attributes": {
          "slug": "spike-spiegel",
          "image": {
            "original": "https://media.kitsu.io/characters/images/2/original.jpg?1483096805"
          }
        }
      },
      "1": {
        "id": "2",
        "type": "anime",
        "links": {
          "self": "https://kitsu.io/api/edge/anime/2"
        },
        "attributes": {
          "slug": "cowboy-bebop-tengoku-no-tobira",
          "posterImage": {
            "tiny": "https://media.kitsu.io/anime/poster_images/2/tiny.jpg?1435249715",
            "small": "https://media.kitsu.io/anime/poster_images/2/small.jpg?1435249715",
            "medium": "https://media.kitsu.io/anime/poster_images/2/medium.jpg?1435249715",
            "large": "https://media.kitsu.io/anime/poster_images/2/large.jpg?1435249715",
            "original": "https://media.kitsu.io/anime/poster_images/2/original.jpg?1435249715"
          }
        }
      },
      "favRank": 2
}

It is expected for this snippet to only contain "0" ("type": "anime") and "favRank".

Unable to recreate this on any other user so far.

User: Anime Library

An in-range update of vue-template-compiler is breaking the build 🚨

Version 2.2.2 of vue-template-compiler just got published.

Branch	Build failing 🚨
Dependency	vue-template-compiler
Current Version	2.2.1
Type	devDependency

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

As vue-template-compiler is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of extract-text-webpack-plugin is breaking the build 🚨

Version 2.1.2 of extract-text-webpack-plugin just got published.

Branch	Build failing 🚨
Dependency	extract-text-webpack-plugin
Current Version	2.1.1
Type	dependency

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

extract-text-webpack-plugin is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v2.1.2

Bug Fixes

index: resolve schemas relative to __dirname (#536) (8766821) (@MirrorBytes)

Commits

The new version differs by 2 commits.

e81b883 chore(release): 2.1.2
8766821 fix(index): resolve schemas relative to __dirname (#536)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue is breaking the build 🚨

Version 2.2.2 of vue just got published.

Branch	Build failing 🚨
Dependency	vue
Current Version	2.2.1
Type	dependency

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

As vue is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.2.2

Fixed

#5037 ssr: fix JSON file path detection in createBundleRenderer
#5043 fix provide/inject for falsy values (@znck via #5044)
#5046 fix v-on .left .right modifiers conflict between keyboard and mouse events
#5055 handle values with circular reference in v-model bindings
#5097 default slot should use fallback content when it contains all whitespace nodes
#5120 fix v-on inline function expression with modifiers

Commits

The new version differs by 43 commits .

d0b8dce [release] 2.2.2
8921d63 [build] 2.2.2
95cd2bd test v-model select with circular reference
e6f89c0 error-detector code style tweak
fc6f181 fix weex model test
9d3ceba also include weex tests in npm test
12870be expose component v-model expression on passed data
06de266 reusing onRE (#5130)
c619b8d remove inline value warnings for checkbox/radio/select also (close #5112)
2e1e809 fix prevent default unit test (#5127)
303824e default slot should use fallback content when it contains all whitespace nodes (fix #5097)
41ef650 remove log
a524919 fix v-on inline function expression with modifiers (fix #5120)
2afaac2 cache vnodes length (#5125)
0bcad13 Reorganize and update PR template (#5106)

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

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue-template-compiler is breaking the build 🚨

Version 2.3.4 of vue-template-compiler just got published.

Branch	Build failing 🚨
Dependency	vue-template-compiler
Current Version	2.3.3
Type	dependency

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

vue-template-compiler is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.3.4

Fixed

#5839 fix memory leak caused by reference to removed vnodes on data.pendingInsert

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Library media box misaligned

Version: 0.3.1-30-g69ff6e8
Operating System: Windows 10
Browser: Chrome
Browser Version: X

This is not aligned right...
http://prntscr.com/f36cit

Steps to replicate:
0. Set locale to NL

User: Coocla33
Go to library
Hover over first library entrie.

User: Manga Library

An in-range update of vue-server-renderer is breaking the build 🚨

Version 2.3.2 of vue-server-renderer just got published.

Branch	Build failing 🚨
Dependency	vue-server-renderer
Current Version	2.3.1
Type	devDependency

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

As vue-server-renderer is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/wopian/hibari/builds/227901902?utm_source=github_status&utm_medium=notification),- ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/wopian/hibari/build/501)

Release Notes

v2.3.2

Components can now access the SSR context as this.$ssrContext
Internal improvements for handling functional *.vue components style SSR injections

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue-template-compiler is breaking the build 🚨

Version 2.3.1 of vue-template-compiler just got published.

Branch	Build failing 🚨
Dependency	vue-template-compiler
Current Version	2.3.0
Type	dependency

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

vue-template-compiler is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/wopian/hibari/build/489),- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/wopian/hibari/builds/227867247?utm_source=github_status&utm_medium=notification)

Release Notes

v2.3.1

Fixed

#5536 fix regression when render function returns null (@gebilaoxiong via #5539)
#5540 vue-server-renderer/server-plugin: ensure assets are unique (@pi0 via #5540)
#5553 vue-server-renderer/server-plugin: avoid swallowing webpack error when entry is not found
#5559 vue-server-renderer: with runInNewContext: false, the bundle is now indeed executed in the same context. The 2.3.0 behavior is still available behind a new option value runInNewContext: 'once'. See docs for more details.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue-template-compiler is breaking the build 🚨

Version 2.3.3 of vue-template-compiler just got published.

Branch	Build failing 🚨
Dependency	vue-template-compiler
Current Version	2.3.2
Type	dependency

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

vue-template-compiler is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details,- ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v2.3.3

Fixed

#5586 fix unecessary input trigger with v-model on change event (@posva via #5589)
#5591 ssr template interpolation should be whitespace-insensitive (@HerringtonDarkholme via ##5597)
#5592 fix regression where text nodes are merged into comment placeholder nodes (@maggiehe via #5593)
#5610 fix Vue.use not chainable when plugin has already been installed, also makes Vue.mixin chainable. (@lzxb via #5610)
#5615 fix scoped slots when used together with v-for
#5618 fix slot elements after v-for being unnecessarily recreated (@gebilaoxiong via #5627)
#5633 fix comment nodes not cloned properly (@pengchongfu via #5633)
#5635 fix async components timeout triggered when already resolved

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of babel-preset-env is breaking the build 🚨

Version 1.5.2 of babel-preset-env just got published.

Branch	Build failing 🚨
Dependency	babel-preset-env
Current Version	1.5.1
Type	dependency

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

babel-preset-env is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v1.5.2

v1.5.2 (2017-06-07)

🐛 Bug Fix

Ensure explicit targets always override browsers key targets (#346) (@existentialism)

browser targets should be overridden by explicit targets, and we inadvertently broke this when we landed string version support.

Commits

The new version differs by 5 commits.

f4ce53c 1.5.2
00490ac Merge pull request #346 from babel/issue345
2896925 Add node 8 to travis (#347)
0017129 Ensure explicit targets always override browsers key targets
e23bd47 README: Add string type as valid node target value (#337) [skip ci]

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of babel-plugin-istanbul is breaking the build 🚨

Version 4.1.3 of babel-plugin-istanbul just got published.

Branch	Build failing 🚨
Dependency	babel-plugin-istanbul
Current Version	4.1.1
Type	devDependency

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

As babel-plugin-istanbul is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/wopian/hibari/build/482),- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/wopian/hibari/builds/227063859?utm_source=github_status&utm_medium=notification)

Commits

The new version differs by 5 commits0.

2bdc94b chore(release): 4.1.3
b10c1cd chore: explicit upgrade of istanbul dependencies (#104)
0d0d46e docs: switch to conventional commits badge
476a455 chore(release): 4.1.2
6f1bc89 chore: explicit update to dependencies (#100)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-html is breaking the build 🚨

Version 2.0.2 of eslint-plugin-html just got published.

Branch	Build failing 🚨
Dependency	eslint-plugin-html
Current Version	2.0.1
Type	devDependency

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

As eslint-plugin-html is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details,- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of webpack is breaking the build 🚨

Version 2.3.1 of webpack just got published.

Branch	Build failing 🚨
Dependency	webpack
Current Version	2.3.0
Type	devDependency

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

As webpack is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 9 commits .

4b9b660 2.3.1
d1cf8b4 Merge pull request #4538 from webpack/feature/error-emit-warning
ec46a0d Merge pull request #4539 from mp4096/master
18566a1 Fixed link to the Traceur repo in README
751fd9b add stack to non-Error error emitted
b1acb2e Merge pull request #4537 from webpack/bugfix/newline-validation
49ccf44 Merge pull request #4536 from webpack/bugfix/issue-4532
10c44e5 fix extra newline in validation
915c150 fix bug in MinChunkSizePlugin

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue-template-compiler is breaking the build 🚨

Version 2.2.6 of vue-template-compiler just got published.

Branch	Build failing 🚨
Dependency	vue-template-compiler
Current Version	2.2.5
Type	devDependency

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

As vue-template-compiler is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.2.6

Fixed

Fixed a memory leak issue when used with vue-router (vuejs/vue-router#1279)
#5265 Warn when no getter is provided to a computed property (@kmc059000 via #5267)

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue-router is breaking the build 🚨

Version 2.5.3 of vue-router just got published.

Branch	Build failing 🚨
Dependency	vue-router
Current Version	2.5.2
Type	dependency

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

vue-router is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/wopian/hibari/build/484),- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/wopian/hibari/builds/227532968?utm_source=github_status&utm_medium=notification)

Release Notes

v2.5.3

Fixed

#1372 fix beforeRouteEnter next callback firing on wrong instance when used with out-in transition
#1381 fix getMatchedComponents error when called with existing route

Commits

The new version differs by 8 commits0.

2ee03a9 [release] 2.5.3
51b7edf [build] 2.5.3
2c6b72f bump deps
23bedc9 fix instance unregistration (fix #1372)
34b9abc do not normalize to if already a route in getMatchedComponents() (fix #1381)
90ba1cc Update getting-started.md (#1363)
c021235 [Korean] Update vue-router 2.5 (#1370)
1ae8da9 [Just Merge Me] Russian Translation Update (history cleared) (#1368)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue-template-compiler is breaking the build 🚨

Version 2.2.5 of vue-template-compiler just got published.

Branch	Build failing 🚨
Dependency	vue-template-compiler
Current Version	2.2.4
Type	devDependency

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

As vue-template-compiler is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.2.5

Fixed

#5191 fix events emitted from updated hook not triggering update (@Kingwl via #5233)
#5209 fix performance tracing issue
#5216 fix Vue.set crashing when used on Arrays with non-number key (@pkaminski via #5216)
#5224 fix v-show not setting inline display property in SSR (@defcc via #5224)
#5223 fix Array values injected via inject option not reactive (@Kingwl via #5229)
#5243 trigger warning when mutating injected bindings (@rayrutjes via #5243)
#5250 fix input[type=password] behavior in IE9 (@ktsn via #5253)

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of extract-text-webpack-plugin is breaking the build 🚨

Version 2.1.1 of extract-text-webpack-plugin just got published.

Branch	Build failing 🚨
Dependency	extract-text-webpack-plugin
Current Version	2.1.0
Type	dependency

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

extract-text-webpack-plugin is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

Release v2.1.1

2.1.1 (2017-06-08)

Bug Fixes

add a not null check for the content property before throwing error (#404) (58dd5d3)
loader: rm unnecessary this.cacheable (caching) (#530) (c3cb091)
don't extract from common async chunks (#508) (e595417)
validation schema (schema-utils) (#527) (dfeb347)

Commits

The new version differs by 13 commits.

0271b39 chore(release): 2.1.1
e595417 fix: don't extract from common async chunks (#508)
a8ae003 chore(package): fix broken links && update devDependencies (#531)
c3cb091 fix(loader): rm unnecessary this.cacheable (caching) (#530)
eaa5236 docs: rm RELEASE.md (#532)
671e35e chore(package): update webpack-sources v0.1.0...1.0.1 (#526)
dfeb347 fix: validation schema (schema-utils) (#527)
d0e88d0 docs(README): add lead-in description (#517)
58dd5d3 fix: add a not null check for the content property before throwing error (#404)
6c50d8e Update README.md (#469)
c63dc04 docs(README): clarify to set allChunks option when using CommonsChunkPlugin (#476)
c40dc64 chore(package): reduce package size (#482)
a284f3a docs(README): fix options table formatting (#478)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Setup Server

Most of the planned stats require many API requests to provide a meaningful result. These should be computed in the background and cached for a week at the least

Goal is to extend the current express setup, creating a REST API and store with mongoDB. This is required for #93

hibari.moe: "Error: TypeError: Cannot read property 'id' of undefined"

I understand that the site "hibari.moe" is a very early alpha, but I felt that I should let you know of this error in case you were unaware of it (which I doubt, however).

Almost any search I have tried to make results in a fraction of a second of a stat display with the Noh-face user icon, which immediately redirects to an error page with the listed error displayed.

An in-range update of git-revision-webpack-plugin is breaking the build 🚨

Version 2.5.1 of git-revision-webpack-plugin just got published.

Branch	Build failing 🚨
Dependency	git-revision-webpack-plugin
Current Version	2.5.0
Type	dependency

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

git-revision-webpack-plugin is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details,- ✅ codeclimate/coverage 1.8% Details,- ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v2.5.1

Small documentation improvement release 9ebcf08

Commits

The new version differs by 2 commits0.

0238fcd 2.5.1
9ebcf08 Promote better the usage options ❤️

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Feed: Filter Posts

View only user posts, group posts, activity updates or reactions.

Feed: Global Feed

An in-range update of vue-server-renderer is breaking the build 🚨

Version 2.3.4 of vue-server-renderer just got published.

Branch	Build failing 🚨
Dependency	vue-server-renderer
Current Version	2.3.3
Type	devDependency

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

As vue-server-renderer is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.3.4

Fixed

#5839 fix memory leak caused by reference to removed vnodes on data.pendingInsert

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue is breaking the build 🚨

Version 2.3.1 of vue just got published.

Branch	Build failing 🚨
Dependency	vue
Current Version	2.3.0
Type	dependency

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

vue is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/wopian/hibari/builds/227877959?utm_source=github_status&utm_medium=notification),- ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/wopian/hibari/build/493)

Release Notes

v2.3.1

Fixed

#5536 fix regression when render function returns null (@gebilaoxiong via #5539)
#5540 vue-server-renderer/server-plugin: ensure assets are unique (@pi0 via #5540)
#5553 vue-server-renderer/server-plugin: avoid swallowing webpack error when entry is not found
#5559 vue-server-renderer: with runInNewContext: false, the bundle is now indeed executed in the same context. The 2.3.0 behavior is still available behind a new option value runInNewContext: 'once'. See docs for more details.

Commits

The new version differs by 11 commits0.

6b4f3da [release] 2.3.1
2355318 [build] 2.3.1
ebd0338 introduce previous behavior as runInNewContext:"once"
cab1b15 avoid swallowing webpack error when entry is not found (fix #5553)
2a1f79d run bundle in the same global context when runInNewContext is false (fix #5559)
9478fde tweak type definition layouting (#5564)
228f0f8 remove unnecessary :any castings due to improved flow checks
3b426ef Fix when functional component render method retrun null (fix #5536) (#5539)
bb7c543 fix #5539: improve isDef type definition (#5549)
1635ca7 [vue-server-renderer] ensure assets are unique (#5540)
d6c070d link to latest info

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Check if small posterImage exists

Trying to load favourites when an entry doesn't have a small posterImage causes the component to throw an error, leaving only the cover and username displayed.

Source: https://kitsu.io/posts/8700369
Source 2: https://kitsu.io/comments/28554319
Ref: https://hb.wopian.me/#/@iandude365
Ref 2: https://hb.wopian.me/#/@FullmetalHagane

TypeError: Cannot read property 'small' of undefined
    at app.13d8659cb7bdb55195a6.js:1
    at a.Wt [as _l] (vendor.55e0bed0487873dd1883.js:1)
    at a.render (app.13d8659cb7bdb55195a6.js:1)
    at a.t._render (vendor.55e0bed0487873dd1883.js:1)
    at a.r (vendor.55e0bed0487873dd1883.js:1)
    at Hr.get (vendor.55e0bed0487873dd1883.js:1)
    at Hr.run (vendor.55e0bed0487873dd1883.js:1)
    at mt (vendor.55e0bed0487873dd1883.js:1)
    at Array.<anonymous> (vendor.55e0bed0487873dd1883.js:1)
    at t (vendor.55e0bed0487873dd1883.js:1)

An in-range update of vue is breaking the build 🚨

Version 2.3.4 of vue just got published.

Branch	Build failing 🚨
Dependency	vue
Current Version	2.3.3
Type	dependency

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

vue is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.3.4

Fixed

#5839 fix memory leak caused by reference to removed vnodes on data.pendingInsert

Commits

The new version differs by 3 commits.

1f9416d [release] 2.3.4
97b07be [build] 2.3.4
33a25e7 prevent data.pendingInsert to keep reference to removed nodes (fix #5839)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue is breaking the build 🚨

Version 2.3.2 of vue just got published.

Branch	Build failing 🚨
Dependency	vue
Current Version	2.3.1
Type	dependency

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

vue is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/wopian/hibari/builds/227902194?utm_source=github_status&utm_medium=notification),- ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/wopian/hibari/build/502)

Release Notes

v2.3.2

Components can now access the SSR context as this.$ssrContext
Internal improvements for handling functional *.vue components style SSR injections

Commits

The new version differs by 4 commits0.

b977c77 [release] 2.3.2
60291f2 [build] 2.3.2
8dc4215 improvements for handling vue-loader functional components with style injections
8d7ad19 expose $ssrContext

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Roadmap

An in-range update of axios is breaking the build 🚨

Version 0.16.1 of axios just got published.

Branch	Build failing 🚨
Dependency	axios
Current Version	0.16.0
Type	dependency

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

As axios is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 20 commits .

5c8095e Releasing 0.16.1
982183c Updating changelog
fa58223 Merge pull request #828 from mzabriskie/feature/return-last-request-in-redirects
a18f039 Merge pull request #829 from jcready/patch-3
df6b46c Add caret
04982a2 Update follow-redirects dependency
19644ba Adding documentation for Buffer data
1883344 support node buffers less than 8192 bytes (#773)
bbfbeff Minor grammar/line length changes (#547)
a784774 Adding comment about header names (#778)
88cc84c Adding documentation for response.request
84d9a41 Adding code to assign the last request to axios response
e5beab0 Adding test checking the request in axios response is the last in a redirect
08eb985 Merge pull request #818 from carlosromel/patch-1
21b43ed Merge pull request #826 from mzabriskie/github-templates

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

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Global Stats

User

Anime & Manga

Titles tracked
Rating distribution - example
Mean completion size (e.g 300 titles)

Anime

Episodes watched

Manga

Chapters read

Feed: Drama Feed

An in-range update of vue is breaking the build 🚨

Version 2.2.5 of vue just got published.

Branch	Build failing 🚨
Dependency	vue
Current Version	2.2.4
Type	dependency

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

As vue is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v2.2.5

Fixed

#5191 fix events emitted from updated hook not triggering update (@Kingwl via #5233)
#5209 fix performance tracing issue
#5216 fix Vue.set crashing when used on Arrays with non-number key (@pkaminski via #5216)
#5224 fix v-show not setting inline display property in SSR (@defcc via #5224)
#5223 fix Array values injected via inject option not reactive (@Kingwl via #5229)
#5243 trigger warning when mutating injected bindings (@rayrutjes via #5243)
#5250 fix input[type=password] behavior in IE9 (@ktsn via #5253)

Commits

The new version differs by 19 commits .

c0ad75b [release] 2.2.5
b876395 [build] 2.2.5
bfeb28f pin todomvc css version
3b7cfc7 coverage
f4630d0 treat with different types as different nodes (fix #5266)
5222f06 bump deps
6de1b9b optimize patch conditionals
0bb529a also warn when listening to camelCase events in in-DOM templates
e47b1e5 Allow named properties on reactive arrays. (#5216)
70db229 handle v-model on password input field on ie9 (fix #5250) (#5253)
23a058e fix(inject): change warn message when trying to mutate an injected value (#5243)
7dea9f1 fix provide isn't reactive with a single array (#5229)
4c4a2ab trigger event after reassigned state - Fix #5191 (#5233)
e733e5c fix SSR v-show render. (#5224)
84856a3 update issue template

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

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue-template-compiler is breaking the build 🚨

Version 2.3.2 of vue-template-compiler just got published.

Branch	Build failing 🚨
Dependency	vue-template-compiler
Current Version	2.3.1
Type	dependency

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

vue-template-compiler is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/wopian/hibari/builds/227901146?utm_source=github_status&utm_medium=notification),- ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/wopian/hibari/build/500)

Release Notes

v2.3.2

Components can now access the SSR context as this.$ssrContext
Internal improvements for handling functional *.vue components style SSR injections

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Error: TypeError: Cannot read property 'id' of undefined

Sorry, don't have time to dig around, but thought I'd post it anyway.

Searching for anime

When searching for anime, hibari throws the error:
Error: TypeError: Cannot read property 'forEach' of undefined
Sounds like a variable isn't being created or maybe was renamed elsewhere?

Feed: Manga Feed

Placeholder content shown when cache older than 30 minutes

When local storage data is older than 30 minutes, the this.error within fetchData() prevents displaying the outdated information while the new data is retrieved. Instead it displays the placeholder content.

https://gfycat.com/WhirlwindLinedCutworm

User Stats

Client side implementation of user stats

User

Anime & Manga

Category breakdown (comedy, drama...)
Type breakdown (tv, movie...)
Titles completed
Mean score
Rating distribution - example
† Completion or activity per month - example or github style
Mean score by year/decade - example

Anime Only

Episodes watched
Rating vs time spent watching - example
Ratings vs episode count - example

Manga Only

Chapters read
Ratings vs chapter count - example

† Requires endpoint in Kitsu's API (hummingbird-me/kitsu-server#77)

An in-range update of shelljs is breaking the build 🚨

Version 0.7.8 of shelljs just got published.

Branch	Build failing 🚨
Dependency	shelljs
Current Version	0.7.7
Type	dependency

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

shelljs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 13 commits.

3864567 0.7.8
a66e338 docs(changelog): updated by Nate Fischer [ci skip]
bbd8178 Add node 8 to CI (#730)
15558cf fix(mkdir): improve error handling around files (#721)
a2e13b6 Properly handle directories as arguments (#713)
951ff22 Add common.buffer (#710)
92d3f39 Fix common.expand error (#709)
bbe521b Fix #631 throw error when overwriting recently created file (#702)
d8ac4d3 refactor: remove unnecessary common.js imports (#703)
7feabda Remove contents of symlink to dir with rm -rf (#688)
e12da9d Refactor: Use process.platform across codebase (#689)
80d590e Small clarification of verbose flag (#691)
b9201eb docs(changelog): updated by Nate Fischer [ci skip]

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of vue is breaking the build 🚨

Version 2.3.3 of vue just got published.

Branch	Build failing 🚨
Dependency	vue
Current Version	2.3.2
Type	dependency

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

vue is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details,- ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes

v2.3.3

Fixed

#5586 fix unecessary input trigger with v-model on change event (@posva via #5589)
#5591 ssr template interpolation should be whitespace-insensitive (@HerringtonDarkholme via ##5597)
#5592 fix regression where text nodes are merged into comment placeholder nodes (@maggiehe via #5593)
#5610 fix Vue.use not chainable when plugin has already been installed, also makes Vue.mixin chainable. (@lzxb via #5610)
#5615 fix scoped slots when used together with v-for
#5618 fix slot elements after v-for being unnecessarily recreated (@gebilaoxiong via #5627)
#5633 fix comment nodes not cloned properly (@pengchongfu via #5633)
#5635 fix async components timeout triggered when already resolved

Commits

The new version differs by 19 commits0.

8d56a49 [release] 2.3.3
6bdaeb0 [build] 2.3.3
aaad733 improve scoped slot test case (#5640)
e70f191 no need to test composition events on Android
38759a6 fix test case in IE
8d54aec async components: timeout should not trigger if already resolved (fix #5635)
3139605 ignore ssr getter
0ccefff support v-for on scoped slots (fix #5615)
dc00590 comments
ec70b44 tweak noramlizeArrayChildren
f2bd882 Fix: nested child elements can not be updated correctly, fix #5618 (#5627)
5d965d5 clone isComment when cloneVNode (#5633)
b5b1ac3 improve mutli-line && coding style to keep consistence (#5625)
1c40e32 Fix use mixin API feat continuous operation (#5610)
ca02043 avoid using native as identifier (close #5623)

There are 19 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

wopian / hibari Goto Github PK

hibari's Introduction

Hibari

Features

Browser Support

Contributing

Development

Requirements

Setup

Commands

Releases

License

hibari's People

Contributors

Stargazers

Watchers

Forkers

hibari's Issues

Version 2.3.3 of vue-server-renderer just got published.

Fixed

Version 2.3.1 of vue-server-renderer just got published.

Fixed

Version 2.2.6 of vue just got published.

Fixed

Version 2.2.2 of vue-template-compiler just got published.

Version 2.1.2 of extract-text-webpack-plugin just got published.

Bug Fixes

Version 2.2.2 of vue just got published.

Fixed

Version 2.3.4 of vue-template-compiler just got published.

Fixed

Version 2.3.2 of vue-server-renderer just got published.

Version 2.3.1 of vue-template-compiler just got published.

Fixed

Version 2.3.3 of vue-template-compiler just got published.

Fixed

Version 1.5.2 of babel-preset-env just got published.

v1.5.2 (2017-06-07)

🐛 Bug Fix

Version 4.1.3 of babel-plugin-istanbul just got published.

Version 2.0.2 of eslint-plugin-html just got published.

Version 2.3.1 of webpack just got published.

Version 2.2.6 of vue-template-compiler just got published.

Fixed

Version 2.5.3 of vue-router just got published.

Fixed

Version 2.2.5 of vue-template-compiler just got published.

Fixed

Version 2.1.1 of extract-text-webpack-plugin just got published.

2.1.1 (2017-06-08)

Bug Fixes

Version 2.5.1 of git-revision-webpack-plugin just got published.

Version 2.3.4 of vue-server-renderer just got published.

Fixed

Version 2.3.1 of vue just got published.

Fixed

Version 2.3.4 of vue just got published.

Fixed

Version 2.3.2 of vue just got published.

Version 0.16.1 of axios just got published.

User

Anime & Manga

Anime

Manga

Version 2.2.5 of vue just got published.

Fixed

Version 2.3.2 of vue-template-compiler just got published.

User

Anime & Manga

Anime Only

Manga Only

Version 0.7.8 of shelljs just got published.

Version 2.3.3 of vue just got published.

Fixed

Recommend Projects

Recommend Topics

Recommend Org