"component" plugin doesnt wait for queued promises on a context before creating instance of a view-model

When following config is provided to a Route class, ComponentViewModel instance is created before promises queued on Context are finished. Results in error in VM constructor if trying to access properties of the Context that would have been set by a callback from a promise.
component: { viewModel: ComponentViewModel, template: template }

Router Init Plugin - Initializing before rendering

Hey Casey,

I'm using the Init plugin and in the documentation it is mentioned that it can be used "to declaratively initialize a viewModel before rendering."

Following the documentation I've added it to my ViewModel as follows:

import ko from "knockout";
import { Route } from "@profiscience/knockout-contrib-router";
import {
  initializerPlugin,
  INITIALIZED
} from "@profiscience/knockout-contrib-router-plugins-init";
import { componentPlugin } from "@profiscience/knockout-contrib-router-plugins-component";
import "regenerator-runtime/runtime";

Route.usePlugin(componentPlugin).usePlugin(initializerPlugin); // **MUST** come after component plugin


function resolveAfter2Seconds() {
  return new Promise(resolve => {
    setTimeout(() => {
      resolve('resolved');
    }, 2000);
  });
}

class DataModel {
  constructor() {
    this[INITIALIZED] = this.init();
    this.init = this.init.bind(this);
  }
  async init() {
    console.log('calling Data Model init');
    await resolveAfter2Seconds();
  }
}

export default class ViewModel {
  constructor(ctx) {
    this.ctx = ctx;
    let user = ctx.params.id
      ? ctx.$parent.users.find(user => user.id === parseInt(ctx.params.id))
      : {};
    this.user = user;
    
    this.isInitialized = ko.observable(false);
    this.data = new DataModel()
    this[INITIALIZED] = this.init(ctx);
    this.init = this.init.bind(this);
  }

  init(ctx) {
    const p = new Promise((resolve, reject) => {
      setTimeout(() => {
        console.log('calling ViewModel init');
        this.isInitialized(true);
        resolve();
      }, 2000);
    });
    return p;
  }
}

When I run this code, I can see the delay between the call to the init on my DataModel and the init on my ViewModel.

Nevertheless, the component is rendered without waiting for the init methods to finish.

My expectation was that it would only render after finishing the initialization on both (DataModel and ViewModel).

Can you help me out understanding it?

Here is a sample on CodeSandBox

Thanks in advance

Plugins have unmet peer dependencies

When installing @profiscience/knockout-contrib-router-plugins-title, I am given the following warning:

warning "@profiscience/[email protected]" has incorrect peer dependency "@profiscience/knockout-contrib-router@^2.0.0-4".

My package.json is as follows:

{
  "version": "1.0.0",
  "name": "asp.net",
  "dependencies": {
    "@profiscience/knockout-contrib-router": "^1.2.0",
    "@profiscience/knockout-contrib-router-plugins-title": "^1.0.0-alpha.7"
    ...
  },
  "devDependencies": {
    ...
  },
  "scripts": {
    ...
  }
}

Why is this happening?

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `10.11.7` to `10.12.0`.

🚨 View failing branch.

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

@types/node 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).

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 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `10.10.1` to `10.10.2`.

🚨 View failing branch.

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

@types/node 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).

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 🌴

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

The devDependency prettier was updated from `1.15.2` to `1.15.3`.

🚨 View failing branch.

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

prettier 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).

Release Notes for 1.15.3

🔗 Changelog

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 🌴

An in-range update of ts-jest is breaking the build 🚨

The devDependency ts-jest was updated from `23.10.1` to `23.10.2`.

🚨 View failing branch.

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

ts-jest 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).

Commits

The new version differs by 44 commits.

13cb48d Merge pull request #764 from huafu/release/23.10.2
aa3e5f7 chore(release): 23.10.2
9db3337 Merge pull request #763 from huafu/wrong-error-if-import-fails
e0d6c57 fix(import): wrong error message when a module exists but fails
e765875 Merge pull request #757 from huafu/testMatch-and-testRegex
a4bbdcd docs(preset): typos
ddc2f79 docs(preset): usage of all presets + note about testMatch
6985e07 Merge branch 'testMatch-and-testRegex' of github.com:huafu/ts-jest into testMatch-and-testRegex
6a72a87 test(cli): test migrate preset detection
febd8d3 feat(cli): CLI 'config:migrate' now detects best preset
f55d895 feat(preset): adds presets typings and export all presets
e409653 Merge branch 'master' into testMatch-and-testRegex
0534889 Merge pull request #759 from kulshekhar/dependabot/npm_and_yarn/@types/node-10.11.0
e23e0be build(deps-dev): bump @types/node from 10.10.3 to 10.11.0
7890162 Merge branch 'master' into testMatch-and-testRegex

There are 44 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 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `10.11.3` to `10.11.4`.

🚨 View failing branch.

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

@types/node 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).

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 🌴

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

The devDependency husky was updated from `1.1.1` to `1.1.2`.

🚨 View failing branch.

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

husky 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).

Commits

The new version differs by 9 commits.

05f57f2 1.1.2
bbacc43 Update CHANGELOG.md
89efe65 Check that HUSKY_DEBUG equals "true"
0177900 Update CHANGELOG.md
ab4a28e Fix "[[: not found"
2c98004 Update package-lock.json
74149bc Update debug message
528c52a Add HUSKY_DEBUG=true to .travis.ym
39678b3 Print debug message at hook start (#377)

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 🌴

Help: How to run the router examples?

Hi,

I would like to try out the new version of the router but I'm not being able to run the examples.

They are in Typescript and I can't find how I'm supposed to transpile it to run them.

Thanks in advance!

An in-range update of ts-jest is breaking the build 🚨

The devDependency ts-jest was updated from `23.10.0` to `23.10.1`.

🚨 View failing branch.

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

ts-jest 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).

Commits

The new version differs by 13 commits.

d9c5b45 Merge pull request #743 from huafu/release/23.10.1
e4a3a09 chore(release): 23.10.1
ab94359 Merge pull request #742 from huafu/fix-740-no-js-compilation-with-allow-js
a844fd4 Merge branch 'master' into fix-740-no-js-compilation-with-allow-js
18dced1 Merge pull request #741 from huafu/e2e-weird-deep-paths
9e7d6a0 test(config): adds test related to allowJs
374dca1 fix(compile): js files were never transpiled thru TS
70fd9af ci(cache): removes some paths from the caching
c12dfff fix(windows): normalize paths
0141098 test(e2e): deep paths and coverage
6ccbff3 Merge pull request #736 from huafu/detect-import-and-throw-if-none
a2a4be2 fix(config): warn instead of forcing ESM interoperability
21644da Merge pull request #735 from huafu/master

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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

An in-range update of jest-fetch-mock is breaking the build 🚨

The devDependency jest-fetch-mock was updated from `1.7.4` to `1.7.5`.

🚨 View failing branch.

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

jest-fetch-mock 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).

Commits

The new version differs by 2 commits.

c207011 1.7.5
bfc2c74 Update readme

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 🌴

Router: "path" and "activePath" bindings could have an option to match child route paths as well.

This is a feature suggestion for Router.
I. e. having route structure.
|-- /page1
|-- /page2
|--- /
|--- /tab2

In order to create a menu for top level paths there is a need to have a bindings "path" and "activePath" that would also match child routes. Current implementation of "activePath" matches full path only, binding doesnt add active path class to "/page2" anchor when current path is "/page2/tab2". This could be an option for an existing binding handlers (both "path" and "activePath"), i.e. <a data-bind="path: '/page2', matchChildrenAsActive: true">page2</a>

Lazy loading with dynamic routes

I've been trying to get your lazy loading solution working for a large project I'm working on and have come across a few problems. The project currently uses history and crossroads for routing, and the main route defined at the app-root component is as follows:

const routes: Route[] = [
    { url: `${Global.AppRoot + Global.AppRouterRoot}/{schema}/:location:/:component:/:id:/` }
];

Would it be possible to use this route with this knockout router and navigate to the dynamic component that is specified in the URL?

If I am to follow the lazy loading example exactly, it would mean me having to specify the exact names of the components per route, instead of them being dynamically registered. This would mean me needing to write a lot of repeated code for a large project. I understand that the plugin included in the example you've provided can be extended but I can't see a way for me to access the route's URL directly to pull out the component name from it.

I'm obviously a newbie to this router, so any info or guidance is much appreciated.

Jamie

Typescript source/definitions issues

Hi,

I was trying to include this library in a typescript project, but maybe I'm missing something in my tsconfig.json because it starts to check source code in this module inside node_modules even excluding "node_modules". maybe is a noobie question about typescript, or it can be done something to improve here, because it tries to check ts files under node_modules/@profiscience/knockout-contrib-* using my tsconfig.json.

I'm using webpack and awesome-typescript-loader, maybe is required to do something here?

An in-range update of tslint-config-prettier is breaking the build 🚨

The devDependency tslint-config-prettier was updated from `1.15.0` to `1.16.0`.

🚨 View failing branch.

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

tslint-config-prettier 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).

Release Notes for v1.16.0

1.16.0 (2018-11-13)

Features

rules: add tslint-react/jsx-space-before-trailing-slash (26cc41c)

Commits

The new version differs by 30 commits.

ca35700 Merge pull request #210 from ikatyang/feat/tslint-react/jsx-space-before-trailing-slash
c9b0900 chore(deps-dev): bump tslint from 5.9.1 to 5.11.0 (#207)
26cc41c feat(rules): add tslint-react/jsx-space-before-trailing-slash
9ffef95 chore(deps-dev): bump tslint-react from 3.5.1 to 3.6.0 (#205)
9d6a542 docs: update repo url and remove unnecessary devDependency (#209)
f5c9451 chore(deps-dev): bump ts-jest from 23.10.0 to 23.10.4 (#203)
3b06abd chore(deps-dev): bump @types/make-dir from 1.0.1 to 1.0.3 (#204)
6b7b9aa chore(deps-dev): bump @types/prettier from 1.10.0 to 1.13.2 (#206)
6514ef4 chore(deps-dev): [security] bump lodash from 4.17.4 to 4.17.11 (#208)
58a3112 chore(package): update prettier to version 1.15.2 (#202)
c07f05a docs(readme): Proper case for TSLint & Prettier (#201)
647fafe chore(package): update prettier to version 1.15.1 (#200)
fa14fb3 chore(package): update prettier to version 1.15.0 (#199)
28d8e8b chore(package): update tslint-consistent-codestyle to version 1.14.1 (#198)
cb4371e chore(package): update tslint-immutable to version 4.9.1 (#197)

There are 30 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 🌴

@profiscience/knockout-contrib-router-plugins-component is logging warnings.

Using this plugin and navigating through routes sometimes I get warning in console:

[@profiscience/knockout-contrib-router-plugins-component] Unable to new viewModel. This may cause unexpected behavior.

Is there a way to disable it? Or is it that I am doing something wrong that I get this warning?

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

The devDependency husky was updated from `1.1.3` to `1.1.4`.

🚨 View failing branch.

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

husky 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).

Commits

The new version differs by 9 commits.

4a9814c 1.1.4
9df8d08 Update CHANGELOG.md
58965b4 Refactor
d32682c Update README.md
3170033 source file (#397)
209a6ea Update CHANGELOG.md
da4d9d2 Upgrade execa to 1.0 (#393)
79e1dd9 Update README.md
f3a923d Update README.md

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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

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

The devDependency lerna was updated from `3.4.1` to `3.4.2`.

🚨 View failing branch.

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

lerna 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).

Release Notes for v3.4.2

Bug Fixes

publish: Prevent retries during access validation so third-party registries are skipped faster (a89ae62)
publish: Use modern auth resolution (7ba41a6)

Commits

The new version differs by 6 commits.

6afcde7 chore(release): publish v3.4.2
bef9a83 chore: bump transitive dependencies
3d68d87 chore: bump dev dependencies
a89ae62 fix(publish): Prevent retries during access validation so third-party registries are skipped faster
7ba41a6 fix(publish): Use modern auth resolution
ef47f2a docs(version): document the —yes option (#1715)

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 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `10.11.4` to `10.11.5`.

🚨 View failing branch.

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

@types/node 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).

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 🌴

Prefix/Suffix feature for knockout-contrib-router-plugins-title

As we had previously discussed, it would be great to be able to configure a prefix and/or suffix to be appended to all route titles.

Thanks!

History state

In the router package, the default behavior of popstate is prevented, and thus the state is not updated. Therefor the history.state cannot really be used (even though it works, as far is I can see, with hashbang:true).
Are there any reason for not replacing current state with the state received from the event?
I can of course make a pull request if you are interested.

Thanks for your great work!
Anders

Running router tests on windows machine gives an error

Tried running "test:router" script and got error.

Any ideas on how to fix it?

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `10.12.6` to `10.12.7`.

🚨 View failing branch.

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

@types/node 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).

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 🌴

An in-range update of @types/jquery is breaking the build 🚨

The devDependency @types/jquery was updated from `3.3.9` to `3.3.10`.

🚨 View failing branch.

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

@types/jquery 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).

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 🌴

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

The devDependency prettier was updated from `1.14.2` to `1.14.3`.

🚨 View failing branch.

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

prettier 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 could not complete due to an error (Details).

Release Notes for 1.14.3

🔗 Changelog

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 🌴

Dynamic component rendering

First of all, thanks for your great work!

I have an application which consist of a navbar and a component, i.e.

<navbar />
<div class="container">
  <router />
</div>

However, on my login page I don't want the navbar and the div.
My solution:

<!-- ko if: authorized -->
<navbar />
<!-- /ko -->
<div id="container">
  <router />
</div>

where I add and remove class container to page depending of authorized (which, of course is an observable). This works most of them time except for when you get logged out without page refresh. What I ideally want is:

<!-- ko if: authorized -->
<navbar />..<router />
<!-- /ko -->
<!-- ko ifnot: authorized -->
<router />
<!-- /ko -->

but since only one instance of <router> is allowed, this is not possible. Of course I could just put the navbar in the components, but it's not their responsibility.

Would you happen to have any (better) suggestions for this?

Best :)

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

The devDependency lerna was updated from `3.4.3` to `3.5.0`.

🚨 View failing branch.

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

lerna 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).

Commits

The new version differs by 48 commits.

1c142db chore(release): publish v3.5.0
fbf9629 refactor(version): Tweak error code when remote branch does not exist
b199f32 refactor(publish): Allow --git-reset to be configured from lerna.json
3b98973 refactor(publish): Gather current tags filtered by --list glob
1aa1712 chore: bump eslint-plugin-jest
f4edc76 docs: Remove broken badges
bc56839 chore: sync protocol of public registry
1a78f1a chore: reset lockfile
3cb7465 fix(publish): Ignore non-release tags when detecting from-git (#1782)
7ee05d7 feat(version): Add --include-merged-tags option (#1712)
e2c0342 docs: Fix link to --git-remote option (#1796) [ci skip]
eae5619 feat(publish): Add option --no-git-reset to leave unstaged changes in working tree (#1791)
b69a728 feat(run): Log package name and timing in runScriptInPackageCapturing (#1781)
9d36654 feat(import) Add --dest option to explicitly specify import destination (#1772)
cd34b48 fix(version): Add friendly error message when remote branch doesn't exist (#1741)

There are 48 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 🌴

Merges into TKO

Would you be interested in contributing some of this to tko / ko4?

An in-range update of @types/jquery is breaking the build 🚨

The devDependency @types/jquery was updated from `3.3.22` to `3.3.23`.

🚨 View failing branch.

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

@types/jquery 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).

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 🌴

An in-range update of @types/lodash is breaking the build 🚨

The devDependency @types/lodash was updated from `4.14.116` to `4.14.117`.

🚨 View failing branch.

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

@types/lodash 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).

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 🌴

An in-range update of ts-jest is breaking the build 🚨

The devDependency ts-jest was updated from `23.10.4` to `23.10.5`.

🚨 View failing branch.

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

ts-jest 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).

Commits

The new version differs by 48 commits.

8cd933b Merge pull request #874 from kulshekhar/release/23.10.5
8742886 chore(release): 23.10.5
1892e1b build(deps-dev): bump @types/babel__core from 7.0.1 to 7.0.2 (#872)
10ff3fd build(deps-dev): bump @types/node from 10.12.0 to 10.12.10 (#883)
0445500 More safely resolve 'jest-config'. (#853)
87ef5b8 Merge pull request #862 from huafu/upgrade-packages
0150319 build(packages): upgrade bs-logger
794b2f2 build(packages): updates e2e test cases dependencies
d325bce build(packages): re-lock semver version above wanted
0abd4d4 build(packages): upgrades external dependencies
04a5ebf Fix security vulnerability (#850)
89269d5 Fix wrong value in package.json example (#849)
0a59b42 Merge pull request #848 from orta/patch-1
9162ebb Update README.md
44948c3 build(deps-dev): bump tslint-plugin-prettier from 2.0.0 to 2.0.1 (#832)

There are 48 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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

An in-range update of pretty-quick is breaking the build 🚨

The devDependency pretty-quick was updated from `1.7.0` to `1.8.0`.

🚨 View failing branch.

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

pretty-quick 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).

Release Notes for v1.8.0

1.8.0 (2018-10-12)

Features

add --verbose flag (#46) (851ddc1)

Commits

The new version differs by 2 commits.

851ddc1 feat: add --verbose flag (#46)
a318e7e docs: update documentation for husky 1.0 (#42)

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 🌴

(router) Routes not reloaded when navigated to with different parameters

Package(s)

router => @profiscience/[email protected]

Describe the bug
I'm not sure if this is intended behavior after the latest update to rc9 or not. I did notice this commit: 6c06eb3.

When on a route, say /customers/23/info and then there is some action on that route Router.update(//customers/56/info);, no errors are thrown and it stays on the original route.

Expected behavior
I'd expect the router to update to the the latest route specified with Router.update. Fwiw, this was working prior to rc9 ( I was on rc8 before this, I even rolled back to verify ). The workaround is to currently pass { force: true }.

Desktop (please complete the following information):

Latest stable version of Chrome

Additional context
Again I'm not sure if this is now the intended behavior or not now. Any insight would be greatly appreciated.

An in-range update of pretty-quick is breaking the build 🚨

The devDependency pretty-quick was updated from `1.6.0` to `1.7.0`.

🚨 View failing branch.

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

pretty-quick 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).

Release Notes for v1.7.0

1.7.0 (2018-09-19)

Features

--no-restage flag for skipping re-stage step in staged mode (#39) (#40) (230d03f)

Commits

The new version differs by 1 commits.

230d03f feat: --no-restage flag for skipping re-stage step in staged mode (#39) (#40)

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 🌴

An in-range update of @types/jest is breaking the build 🚨

The devDependency @types/jest was updated from `23.3.9` to `23.3.10`.

🚨 View failing branch.

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

@types/jest 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).

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 🌴

An in-range update of @types/jquery is breaking the build 🚨

The devDependency @types/jquery was updated from `3.3.11` to `3.3.12`.

🚨 View failing branch.

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

@types/jquery 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).

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 🌴

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

The devDependency lerna was updated from `3.4.0` to `3.4.1`.

🚨 View failing branch.

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

lerna 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).

Commits

The new version differs by 10 commits.

05a27a6 chore(release): publish v3.4.1
f7fdc77 fix(publish): Overwrite Yarn registry proxy when encountered
06a9479 fix(publish): Set token on npm config, allow third-party registries to remain non-compliant
987fd26 fix(bootstrap): Constrain npm-conf argument object to options.registry only
597606c fix(add): Allow --registry option
25af71d fix(npm-conf): Do not overwrite defaults with undefined cli keys
159a0b0 fix(conventional-commits): Upgrade angular preset, ensure header is not duplicated
9752f3e fix(conventional-commits): Upgrade dependencies
a60a0c3 docs: Add 'lerna create' command to README.md (#1680)
265ec0c docs(readme): update independent mode instructions (#1701)

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 🌴

An in-range update of @types/jest is breaking the build 🚨

The devDependency @types/jest was updated from `23.3.2` to `23.3.3`.

🚨 View failing branch.

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

@types/jest 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).

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 🌴

An in-range update of @types/jest is breaking the build 🚨

The devDependency @types/jest was updated from `23.3.3` to `23.3.4`.

🚨 View failing branch.

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

@types/jest 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).

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 🌴

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

The devDependency husky was updated from `1.1.0` to `1.1.1`.

🚨 View failing branch.

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

husky 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).

Commits

The new version differs by 8 commits.

09bbaa3 1.1.1
86379ab Update CHANGELOG.md
f588dac Update CHANGELOG.md
dd57ab7 Check Node version before running hook
821d88d Update CHANGELOG.md
c6b9925 Merge branch 'master' of https://github.com/typicode/husky
1406071 Check HUSKY_SKIP_INSTALL value before other checks
cb9a517 Update BACKERS.md

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 🌴

An in-range update of ts-jest is breaking the build 🚨

The devDependency ts-jest was updated from `23.1.4` to `23.10.0`.

🚨 View failing branch.

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

ts-jest 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 could not complete due to an error (Details).

Release Notes for 23.10.0

`ts-jest`, reloaded!

lots of new features including full type-checking and internal cache (see changelog)
improved performances
Babel not required anymore
improved (and growing) documentation
a ts-jest Slack community where you can find some instant help
end-to-end isolated testing over multiple jest, typescript and babel versions

Commits

The new version differs by 293 commits.

0e5ffed chore(release): 23.10.0
3665609 Merge pull request #734 from huafu/appveyor-optimizations
45d44d1 Merge branch 'master' into appveyor-optimizations
76e2fe5 ci(appveyor): cache npm versions as well
191c464 ci(appveyor): try to improve appveyor's config
0f31b42 Merge pull request #733 from huafu/fix-test-snap
661853a Merge branch 'master' into fix-test-snap
aa7458a Merge pull request #731 from kulshekhar/dependabot/npm_and_yarn/tslint-plugin-prettier-2.0.0
70775f1 ci(lint): run lint scripts in series instead of parallel
a18e919 style(fix): exclude package.json from tslint rules
011b580 test(config): stop using snapshots for pkg versions
7e5a3a1 build(deps-dev): bump tslint-plugin-prettier from 1.3.0 to 2.0.0
fbe90a9 Merge pull request #730 from kulshekhar/dependabot/npm_and_yarn/@types/node-10.10.1
a88456e build(deps-dev): bump @types/node from 10.9.4 to 10.10.1
54fd239 Merge pull request #729 from kulshekhar/dependabot/npm_and_yarn/prettier-1.14.3

There are 250 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 🌴

An in-range update of @types/jquery is breaking the build 🚨

The devDependency @types/jquery was updated from `3.3.10` to `3.3.11`.

🚨 View failing branch.

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

@types/jquery 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).

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 🌴

Need some help moving from ko-contrib-router to knockout-contrib-router 2

Hi Casey,

We’ve recently started migrating from ko-component-router to knockout-contrib-router and there are some things we noticed and wanted to know if they are bugs or behavior misunderstandings from our side.

I’ve created a codesandbox project where every single issue reported below can be reproduced. Here’s the demo link: https://p938k153rj.codesandbox.io/user
You can check the code at https://codesandbox.io/s/p938k153rj

Difficulties with the Path Binding (:heavy_check_mark: - @caseyWebb)

From the second router level below, we are no longer able to use the path bind ./, to access child routes, we must add the hardcoded path instead, or work around it using the canonicalPath.
This is indicated in the green/red text: https://p938k153rj.codesandbox.io/user/new/details
The path binding seems to work well for the first level, but not for the second and below.

Children component re-renders when clicking on href for the same route

From the second router level below, when we hit the same navigation item it re-renders the child component. This doesn’t happen at the top level.

In order to test this, click on the ‘Users’ link multiple times. You will notice that the first level “rendered at X ms message” is always the same. This is the expected behavior for me: clicking on the same link doesn’t trigger a re-rendering. It also works fine for the second level ‘New’ and ‘Edit’ navigation items.

But if you click on the ‘Details’ or ‘Contact’ the child component gets re-rendered, every time you click them.

Here is a sample video of this behavior: https://www.screencast.com/t/xmgbuWLKWav

Also, I’ve noticed that the first time I click on the ‘Users’ link the browser navigates to ‘/user’. The second time I click on it, the browser navigates to ‘/user/’.

Let me just say thank you for the router. The newer version is way better and a lot cleaner.

An in-range update of @types/jquery is breaking the build 🚨

The devDependency @types/jquery was updated from `3.3.6` to `3.3.7`.

🚨 View failing branch.

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

@types/jquery 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 could not complete due to an error (Details).

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 🌴

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

The devDependency karma was updated from `3.1.1` to `3.1.2`.

🚨 View failing branch.

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

karma 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).

Release Notes for v3.1.2

Bug Fixes

browser: report errors to console during singleRun=false (#3209) (30ff73b), closes #3131
changelog: remove release which does not exist (#3214) (4e87902)
dep: Bump useragent to fix HeadlessChrome version (#3201) (240209f), closes #2762
deps: upgrade sinon-chai 2.x -> 3.x (#3207) (dc5f5de)
file-list: do not preprocess up-to-date files (#3196) (5334d1a), closes #2829
package: bump lodash version (#3203) (d38f344), closes #3177
server: use flatted for json.stringify (#3220) (fb05fb1), closes #3215

Features

docs: callout the key debug strategies. (#3219) (2682bff)

Commits

The new version differs by 11 commits.

7d4d347 chore: release v3.1.2
5077c18 chore: update contributors
fb05fb1 fix(server): use flatted for json.stringify (#3220)
2682bff feat(docs): callout the key debug strategies. (#3219)
4e87902 fix(changelog): remove release which does not exist (#3214)
30ff73b fix(browser): report errors to console during singleRun=false (#3209)
5334d1a fix(file-list): do not preprocess up-to-date files (#3196)
dc5f5de fix(deps): upgrade sinon-chai 2.x -> 3.x (#3207)
d38f344 fix(package): bump lodash version (#3203)
ffb41f9 refactor(browser): log state transitions in debug (#3202)
240209f fix(dep): Bump useragent to fix HeadlessChrome version (#3201)

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 🌴

An in-range update of ts-jest is breaking the build 🚨

The devDependency ts-jest was updated from `23.10.3` to `23.10.4`.

🚨 View failing branch.

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

ts-jest 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).

Release Notes for 23.10.4 (2018-10-06)

Bug Fixes

cache: adds project's dep versions to cache key (6cacbea), closes #785
cli: change options to better reflect the new presets (68abcfb)
helpers: deprecate import from ts-jest, now ts-jest/utils (33ff29f), closes #782
typings: typo in presets definition file (53767ab)
typings: wrong import in preset typings + test (94dc4e7)

Commits

The new version differs by 22 commits.

ef89ee6 Merge pull request #795 from huafu/release/23.10.4
82a930b chore(release): 23.10.4
69b80ad Merge pull request #794 from huafu/fix-preset-typings
94dc4e7 fix(typings): wrong import in preset typings + test
53767ab fix(typings): typo in presets definition file
90beca8 Merge pull request #787 from huafu/fix-testing-utils
89ad06a style(cli): more readable code when setting defaults for init
b1eed98 docs(install): includes @types/jest in install script
b837acd test(typings): repalce jest.SpyInstance with MockInstance
6cacbea fix(cache): adds project's dep versions to cache key
7b2dd01 test(preset): fixes tests, doc and cli for presets
ec78757 docs(utils): updates docs related to moved helpers
8d5a60a test(preset): updates tests related to presets
68abcfb fix(cli): change options to better reflect the new presets
33ff29f fix(helpers): deprecate import from ts-jest, now ts-jest/utils

There are 22 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 🌴

profiscience / knockout-contrib Goto Github PK

knockout-contrib's Introduction

@profiscience/knockout-contrib

knockout-contrib's People

Contributors

Stargazers

Watchers

Forkers

knockout-contrib's Issues

The devDependency @types/node was updated from 10.11.7 to 10.12.0.

The devDependency @types/node was updated from 10.10.1 to 10.10.2.

The devDependency prettier was updated from 1.15.2 to 1.15.3.

The devDependency ts-jest was updated from 23.10.1 to 23.10.2.

The devDependency @types/node was updated from 10.11.3 to 10.11.4.

The devDependency husky was updated from 1.1.1 to 1.1.2.

The devDependency ts-jest was updated from 23.10.0 to 23.10.1.

The devDependency jest-fetch-mock was updated from 1.7.4 to 1.7.5.

The devDependency tslint-config-prettier was updated from 1.15.0 to 1.16.0.

1.16.0 (2018-11-13)

Features

The devDependency husky was updated from 1.1.3 to 1.1.4.

The devDependency lerna was updated from 3.4.1 to 3.4.2.

Bug Fixes

The devDependency @types/node was updated from 10.11.4 to 10.11.5.

The devDependency @types/node was updated from 10.12.6 to 10.12.7.

The devDependency @types/jquery was updated from 3.3.9 to 3.3.10.

The devDependency prettier was updated from 1.14.2 to 1.14.3.

The devDependency lerna was updated from 3.4.3 to 3.5.0.

The devDependency @types/jquery was updated from 3.3.22 to 3.3.23.

The devDependency @types/lodash was updated from 4.14.116 to 4.14.117.

The devDependency ts-jest was updated from 23.10.4 to 23.10.5.

The devDependency pretty-quick was updated from 1.7.0 to 1.8.0.

1.8.0 (2018-10-12)

Features

The devDependency pretty-quick was updated from 1.6.0 to 1.7.0.

1.7.0 (2018-09-19)

Features

The devDependency @types/jest was updated from 23.3.9 to 23.3.10.

The devDependency @types/jquery was updated from 3.3.11 to 3.3.12.

The devDependency lerna was updated from 3.4.0 to 3.4.1.

The devDependency @types/jest was updated from 23.3.2 to 23.3.3.

The devDependency @types/jest was updated from 23.3.3 to 23.3.4.

The devDependency husky was updated from 1.1.0 to 1.1.1.

The devDependency ts-jest was updated from 23.1.4 to 23.10.0.

ts-jest, reloaded!

The devDependency @types/jquery was updated from 3.3.10 to 3.3.11.

Difficulties with the Path Binding (:heavy_check_mark: - @caseyWebb)

Children component re-renders when clicking on href for the same route

The devDependency @types/jquery was updated from 3.3.6 to 3.3.7.

The devDependency karma was updated from 3.1.1 to 3.1.2.

Bug Fixes

Features

The devDependency ts-jest was updated from 23.10.3 to 23.10.4.

Bug Fixes

Recommend Projects

Recommend Topics

Recommend Org

Jobs

The devDependency @types/node was updated from `10.11.7` to `10.12.0`.

The devDependency @types/node was updated from `10.10.1` to `10.10.2`.

The devDependency prettier was updated from `1.15.2` to `1.15.3`.

The devDependency ts-jest was updated from `23.10.1` to `23.10.2`.

The devDependency @types/node was updated from `10.11.3` to `10.11.4`.

The devDependency husky was updated from `1.1.1` to `1.1.2`.

The devDependency ts-jest was updated from `23.10.0` to `23.10.1`.

The devDependency jest-fetch-mock was updated from `1.7.4` to `1.7.5`.

The devDependency tslint-config-prettier was updated from `1.15.0` to `1.16.0`.

The devDependency husky was updated from `1.1.3` to `1.1.4`.

The devDependency lerna was updated from `3.4.1` to `3.4.2`.

The devDependency @types/node was updated from `10.11.4` to `10.11.5`.

The devDependency @types/node was updated from `10.12.6` to `10.12.7`.

The devDependency @types/jquery was updated from `3.3.9` to `3.3.10`.

The devDependency prettier was updated from `1.14.2` to `1.14.3`.

The devDependency lerna was updated from `3.4.3` to `3.5.0`.

The devDependency @types/jquery was updated from `3.3.22` to `3.3.23`.

The devDependency @types/lodash was updated from `4.14.116` to `4.14.117`.

The devDependency ts-jest was updated from `23.10.4` to `23.10.5`.

The devDependency pretty-quick was updated from `1.7.0` to `1.8.0`.

The devDependency pretty-quick was updated from `1.6.0` to `1.7.0`.

The devDependency @types/jest was updated from `23.3.9` to `23.3.10`.

The devDependency @types/jquery was updated from `3.3.11` to `3.3.12`.

The devDependency lerna was updated from `3.4.0` to `3.4.1`.

The devDependency @types/jest was updated from `23.3.2` to `23.3.3`.

The devDependency @types/jest was updated from `23.3.3` to `23.3.4`.

The devDependency husky was updated from `1.1.0` to `1.1.1`.

The devDependency ts-jest was updated from `23.1.4` to `23.10.0`.

`ts-jest`, reloaded!

The devDependency @types/jquery was updated from `3.3.10` to `3.3.11`.

The devDependency @types/jquery was updated from `3.3.6` to `3.3.7`.

The devDependency karma was updated from `3.1.1` to `3.1.2`.

The devDependency ts-jest was updated from `23.10.3` to `23.10.4`.