Release/8.4.0 (#34)

Release 8.4.0. See CHANGELOG for details.

Author: Thesephi

.gitignore

@@ -30,3 +30,6 @@ node_modules
 
 .tmp
 deprecated
+
+# local pack (`npm pack` result)
+somnus-*.tgz

.npmignore

@@ -3,10 +3,16 @@ scripts
 .babelrc
 .travis.yml
 .github
-webpack.config.js
+webpack.config.ts
 tslint.json
 
 .tmp
 deprecated
 test
 examples
+
+# local pack (`npm pack` result)
+somnus-*.tgz
+
+# GitHub file
+_config.yml

CHANGELOG.md

@@ -1,3 +1,11 @@
+## [8.4.0] - 2022-07-11
+### Changed
+- truly decoupled `unit-http` from `somnus` in user-land (see https://github.com/somnusjs/somnus/issues/33)
+- upgraded a few dependencies
+
+### Added
+- the command `npm run local-pack` which prepares a somnus tarball for local installation (wraps `npm pack`)
+
 ## [8.3.2] - 2022-05-30
 ### Changed
 - GitHub Action config now supports both registries: npm (stable usage) and GitHub Packages (experimental usage)

README.md

@@ -111,6 +111,18 @@ npm test
 
 Why do we run tests for both `src` and `lib` directories? Because as library authors, we're responsible for ensuring that the build process transpiles & outputs as it should, and the best way to do that is by testing the code from both source and dist.
 
+## How to install 'unit-http'?
+
+Integration with Nginx's `unit-http` was added in `v8.2.0` and a rudimentary unit test suite for it was added in `v8.4.0`.
+It is not required to have `unit-http` installed to develop somnus.js; however, if you really want to install `unit-http`,
+feel free to follow the following example steps:
+1. install the corresponding native system dependencies: https://unit.nginx.org/installation/
+2. install the `unit-http` Node.js module itself using `npm i -g unit-http`
+3. link the global `unit-http` to the somnus project using `npm link unit-http`
+
+Note that the instruction above is for example only. It should work for most use cases, but you are free to
+install `unit-http` however best fits your project/system setup.
+
 ## Migration
 
 ### from v3 to v8