use single CI system

* "travis" is now used for building on windows, so "appveyor" got dropped

.travis.yml

@@ -1,27 +1,59 @@
-# https://docs.travis-ci.com/user/customizing-the-build/
-
 branches:
   only:
-    - master
+    - "master"
+language: node_js
+node_js:
+  - "lts/*"
 os:
   - linux
   - osx
-sudo: false
-language: node_js
-node_js:
-  - "8"
-  - "10"
 cache:
   yarn: true
 before_install:
   - | # installing the most recent yarn version
     curl -o- -L https://yarnpkg.com/install.sh | bash;
     export PATH="$HOME/.yarn/bin:$PATH";
 install:
-  - yarn install --pure-lockfile
+  - yarn install --pure-lockfile --network-timeout 1000000
   - yarn add rxjs@6
 script:
+  - npx envinfo
   - node --version
   - npm --version
   - yarn --version
   - yarn run lib
+jobs:
+  # fast_finish: true
+  include:
+    - &windows
+      stage: "Windows"
+      os: windows
+      # tackle travis job finishing issue: "tar: C\:\\Users\travis\\AppData\\Local\\Yarn\\Cache: Cannot stat: No such file or directory"
+      cache: false
+      env:
+        # prevent the following error: No output has been received in the last 10m0s
+        # https://travis-ci.community/t/build-doesnt-finish-after-completing-tests/288/9
+        - YARN_GPG=no
+      before_install:
+        - powershell Get-Process
+        - echo $(where.exe node.exe)
+        - echo $(yarn cache dir)
+        # enable running local PowerShell scripts
+        - powershell -Command 'Set-ExecutionPolicy -ExecutionPolicy RemoteSigned'
+        - | # tackle the performance issue of "yarn install" execution, see https://travis-ci.community/t/current-known-issues-please-read-this-before-posting-a-new-topic/264/15
+          export NODEPATH=$(where.exe node.exe)
+          export PROJECTDIR=$(pwd)
+          export YARNCACHE=$(yarn cache dir)
+          export TEMPDIR=$LOCALAPPDATA\\Temp
+          powershell Add-MpPreference -ExclusionProcess ${NODEPATH}
+          powershell Add-MpPreference -ExclusionPath ${YARNCACHE}
+          powershell Add-MpPreference -ExclusionPath ${PROJECTDIR}
+          powershell Add-MpPreference -ExclusionPath ${TEMPDIR}
+          echo "DisableArchiveScanning..."
+          powershell Start-Process -PassThru -Wait PowerShell -ArgumentList "'-Command Set-MpPreference -DisableArchiveScanning \$true'"
+          echo "DisableBehaviorMonitoring..."
+          powershell Start-Process -PassThru -Wait PowerShell -ArgumentList "'-Command Set-MpPreference -DisableBehaviorMonitoring \$true'"
+          echo "DisableRealtimeMonitoring..."
+          powershell Start-Process -PassThru -Wait PowerShell -ArgumentList "'-Command Set-MpPreference -DisableRealtimeMonitoring \$true'"
+    - <<: *windows
+      node_js: "lts/*"

README.md

@@ -1,12 +1,12 @@
 # electron-rpc-api
 
-[![Build Status: Linux / MacOS](https://travis-ci.org/vladimiry/electron-rpc-api.svg?branch=master)](https://travis-ci.org/vladimiry/electron-rpc-api) [![Build status: Windows](https://ci.appveyor.com/api/projects/status/p5ng54wv0mlc3g4x?svg=true)](https://ci.appveyor.com/project/vladimiry/electron-rpc-api)
+[![Build Status](https://travis-ci.org/vladimiry/electron-rpc-api.svg?branch=master)](https://travis-ci.org/vladimiry/electron-rpc-api)
 
 Is a wrapper around the Electron's IPC for building type-safe API based RPC-like and reactive interactions.
 
 You describe an API structure and communication channel only once creating an API Service instance and then you share that instance between provider and client. It means that API method names and types of the input/return parameters on the client side are the same as on the provider side, so you get a type-safety on both sides having no overhead in runtime, thanks to TypeScript.
 
-This module provides services for interacting with `ipcMain` and `webview` providers factory-like functions of which can be imported like this `import {createIpcMainApiService, createWebViewApiService} from "electron-rpc-api"`.
+The module provides `createIpcMainApiService` and `createWebViewApiService` factory-like functions that can be used to create respective service instances.
 
 ## Getting started
 

example/electron-app/package.json

@@ -26,7 +26,7 @@
     "start:web": "cross-env NODE_ENV=development webpack-dev-server -c ./webpack.config.ts"
   },
   "dependencies": {
-    "electron-rpc-api": "5.0.0-beta1",
+    "electron-rpc-api": "5.0.0",
     "rxjs": "6.5.2",
     "sanitize-html": "1.20.1",
     "tcp-ping": "0.1.1"
@@ -49,10 +49,10 @@
     "electron": "4.2.0",
     "electron-builder": "20.40.2",
     "html-webpack-plugin": "3.2.0",
-    "husky": "2.2.0",
+    "husky": "2.3.0",
     "import-sort-cli": "6.0.0",
     "import-sort-parser-typescript": "6.0.0",
-    "lint-staged": "8.1.6",
+    "lint-staged": "8.1.7",
     "mini-css-extract-plugin": "0.6.0",
     "node-sass": "4.12.0",
     "npm-run-all": "4.1.5",
@@ -64,7 +64,7 @@
     "tslint": "5.16.0",
     "tslint-microsoft-contrib": "6.1.1",
     "tslint-rules-bunch": "0.0.7",
-    "typescript": "3.2.2",
+    "typescript": "3.4.5",
     "wait-on": "3.2.0",
     "webpack": "4.31.0",
     "webpack-cli": "3.3.2",

example/electron-app/tslint.json

@@ -5,7 +5,6 @@
     "./tslint-rules-bunch.json"
   ],
   "rules": {
-    "no-unused-variable": false,
     "max-line-length": [
       true,
       140