DEV Community: JerDox

Create a Websocket client in Javascript using a web worker

JerDox — Tue, 22 Apr 2025 08:55:22 +0000

This is a short tutorial on how to create a JavaScript WebSocket client that runs in a Web Worker.

The finished files can be downloaded at: github

Introduction:

The goal is to exchange data between a WebSocket server and the web client in real time. I decided to use a Web Worker to outsource the handling of the WebSocket data flow from the main thread,
to reducing the communication load.
I also implemented a reconnection logic, since the connection could not be establish or was closed unexpectedly

We will create two files:

index.html: contains the load of the web worker and processing datas from the WebSocket connection

websocketHandler.worker.js: The web worker file, handling of the WebSocket connection and datas

Short infos to Web workers

A web worker...

runs in a separate thread, independent from your web browser's main thread

cannot access or manipulate the DOM

communicates with the main thread using messages via "postMessage"

runs in a separate .js file

Creating the Websocket client

Let's start by creating a JavaScript file named websocketHandler.worker.js
At the top, we’ll add some variables that we’ll use later

let socket = null; // contains the socket object
let shouldReconnect = true; // a flag when we want to auto reconnect
let reconnectTimeout = null; // contains the reconnect timer
let wsServerUrl = '' // the URL to our WebSocket server

Next we add a "onmessage" event function for handling incoming messages to the web worker.

onmessage = function (e) {   
    const data = e.data;
    handlingWebSocket(data);
};

This will be triggered when a message sent to the web worker. The format for this messages will be: wsWorker.postMessage({ type: '<will be connect, send or disconnect>', payload: '<datas of the message>' });

Create also a function handlingWebSocket(data); for processing the WebSocket interface

function handlingWebSocket(data) {}

Now in this function, we create a handling of the different incoming messages-types (connect, send, disconnect). For this create a switch-case for the different message-types:

 switch (data.type) {
    case 'connect':
        // Logic to open the connection to the websocket server
        break;

    case 'send':
        // sending a message to the web socket server
        break;

    case 'disconnect':
        // disconnet and do some clean up
        break;
    }
}

Let's fill the different cases.

Case: connect - Connect to the Websocket server.

When message of type "connect" wsWorker.postMessage({ type: 'connect', wsServerUrl: 'ws://192.168.100.150:4040' }); is coming to the web worker,
we check if still a connection is open, clean the socket object for safty and then call a seperated connectToWebsocket function.

case 'connect':
    // save URL in local variable
    wsServerUrl = data.wsServerUrl

    // set auto reconnect, so when a connection could not be established it will try to reconnect again
    shouldReconnect = true

    // be sure that there is not still a WebSocket server object
    if (socket && socket.readyState !== WebSocket.CLOSED && socket.readyState !== WebSocket.CLOSING) {
        return;
    }

    // to be save the object is empty
    socket = null;

    // call the function to open the connection
    connectToWebSocket(wsServerUrl);
    break;

Then we create and fill the connectToWebsocket function

function connectToWebSocket(wsServerUrl) {
    console.dir("Start connection to WebsocketServer...");

    // open the connection to the WebSocket server
    socket = new WebSocket(wsServerUrl);

    // event which triggered when the connection has been established
    socket.onopen = () => {
        // clear the timeout when the connection was established
        clearTimeout(reconnectTimeout);

        // send message to parent function that the connection was established
        postMessage({ type: 'connected' });
    };

    // event when a message comes from the WebSocket server
    socket.onmessage = (event) => {
        try {
            const msgContent = JSON.parse(event.data);
            postMessage({ type: 'data', payload: msgContent });
        } catch (err) {
            postMessage({ type: 'error', payload: "Error at parsing message datas" });
        }
    };

    // event will be triggered when an error with the WebSocket interfaces raised
    socket.onerror = (err) => {
        postMessage({ type: 'error', payload: err.message });
    };

    // event which triggered when the connection to the WebSocket server will be closed
    socket.onclose = () => {
        postMessage({ type: 'closed' });

        // clean up before try to reconnect
        disposeWebSocket()   

        // check if reconnection should be running
        if (shouldReconnect) {
            postMessage({ type: 'reconnect' });

            // set a timeout every 5sec for trying to reconnect
            reconnectTimeout = setTimeout(
            () => connectToWebSocket(wsServerUrl),
                5000);
        }     
    };
}

We also have to create a dispose function "disposeWebSocket()" to do a clean up

function disposeWebSocket() {
    clearTimeout(reconnectTimeout);

    if (socket) {
        socket.onopen = null;
        socket.onmessage = null;
        socket.onerror = null;
        socket.onclose = null;

        socket = null;
    }
}

Case: send - Next we fill the case for sending datas to the WebSocket sever. We check if the connection is still open before we send datas.

case 'send':
    // check if the connection still open before sending datas
    if (socket && socket.readyState === WebSocket.OPEN) {
        socket.send(JSON.stringify(data.payload));
    }
    break;

Case: disconnect - Finally we create the case for disconnecting from the WebSocket server. We call this when we leave the page or the communication should be ending.

case 'disconnect':
    // prevent auto reconnect when the connection was active closed
    shouldReconnect = false

    if (socket) {
        // we call the close method and pass a status code.
        // code 1000 means normal closure
        socket.close(1000, "Client closing connection");
        console.dir("Sent CLOSE-connection request to server");
    }

    // call the dispose function to clean up
    disposeWebSocket();

    // set the command to end up the web worker semselfe
    self.close();

    break;

As next we'll create the logic for using our WebSocket web worker

First create the index.html file with a default base structure like this:

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title>WebSocket Worker Demo</title>
</head>
<body>
    <h2>WebSocket Worker</h2>
    <div id="status">Connecting...</div>

    <!-- Button for sending datas to the websocket server -->
    <button onclick="sendDatasToWss()">send datas to WSS</button>

    <script>
        // here we palce the logig for the websocket interface
    </script>
</body>
</html>

Inside the "srcipt" tag we start with create the web worker object

const wsWorker = new Worker('websocketHandler.worker.js');

We use the object and send a postMessage of type: "connect" to call the web worker to connect to the WebSocket server like this:

wsWorker.postMessage({ type: 'connect', wsServerUrl: 'ws://192.168.100.150:4040' });

Then we add a handling for messages from the web worker

wsWorker.onmessage = (event) => {
    const { type, payload } = event.data;
    const statusEl = document.getElementById('status');

    if (type === 'connected') {
        statusEl.textContent = "#### CONNECTION to WebSocketServer ESTABLISHED ####";
    } else if (type === 'data') {
        console.dir('Data incomming: ' + JSON.stringify(payload));
    } else if (type === 'error') {
        statusEl.textContent = "Error: " + JSON.stringify(payload);
    } else if (type === 'closed') {
        statusEl.textContent = "WebSocket is closed";
    }else if (type === 'reconnect'){
        statusEl.textContent = "Connection to WebSocketServer closed - Try to reconnect...";
    }
};

We also add a function to test the sending of datas to the websocket server

function sendDatasToWss(){
    console.log("Sending datas to WSS");
    wsWorker.postMessage({ type: 'send', msgContent: 'SomeDatas you need in the WSS' });
}

Do a clean up when the page will be leave

window.addEventListener('beforeunload', () => {
    wsWorker.postMessage({ type: 'disconnect' });

    // Give the worker time to clean up before terminate the web worker
    setTimeout(
        () => wsWorker.terminate(),
    10);
});

When we now open the index.html file and the WebSocket connection should be established.

We see what's happening in the <div id="status">Connecting...</div> on the page.

Symfony - Webpage drops error after installing API-Platfrom

JerDox — Tue, 21 Jun 2022 16:05:54 +0000

After I made it to install the API-Platform and create an entity with the maker-bundle and also updated Symfony to version 4.4, I get an error when I open my webpage.

And although that I activate the debugging mode, I don't get a proper error message, that's sucks....

In the passt I often getting a more detailed error message when by running:

php bin/console clear:cache

...and yes this time too. The error message said:

In FileLoader.php line 180: 

  There is no builtin action for the collection GET operation. You need to define the controller yourself in . (which is being imported from "<path>\config/routes/api_platform.yaml"). Make sure there is a loader supporting the "api_platform" type.  

In ApiLoader.php line 177:

  There is no builtin action for the collection GET operation. You need to define the controller yourself.

I don't know where the problem comes from and this time googleing gets also no helpful links...

So and now ???

I remember that I have updating Symfony the dependencies to the Symfony version 4.4. But the api-platform/core was not updated to a new version, it was still on version "2.1"

So I decide to update this and all the other dependencies.

There for in my composer.json I changed the version of the api-platform/core from "2.1" to "^2.1" to let composer decide which version should be installed.

I save the file and run the command:

composer update --with-all-dependencies

As it runs it ends up with an error:

 Could not delete C:\Users\userap\Desktop\_Workspace\WebDevelopment\WebClient_2\dosierung\vendor/sensio/framework-extra-bundle\Resources\config:   
  This can be due to an antivirus or the Windows Search Indexer locking the file while they are analyzed

Okay the last sentence sounds plausible to me. Means that a service from Windows has just access the file in the moment when composer want to do some changes.

So no problem, I run it again and this time it works, perfect.

Composer has updated the api-platform/core to the version "2.6.8"

I open my webpage and...YES the 500 error is gone and my page was loading, lucky again.

Symfony 4.2 - Creating an entity with the maker-bundle and migrate it

JerDox — Tue, 21 Jun 2022 13:55:00 +0000

After I installed the API-Platfrom in my last Post, I'd like to create an entity which I want to used for a new web service.

My setup is:

php 7.1.3
Symfony 4.2 (later 4.4)
API-Platfrom/core 2.1
maker-bundle 1.12
Doctrine ORM 2.7

Behind the scenes I used the MS SQL Server 2016 as Database.

With the maker-bundle it should be easy to create a new entity by using composer.

So let's start. In the Terminal run:

php bin/console make:entity

After pressing Enter the Terminal will ask you some Question to create that entity.

Q1:
Class name of the entity to create or update (e.g. DeliciousPuppy):
-> apiTest

Q2:
Mark this class as an API Platform resource (expose a CRUD API for it) (yes/no) [no]:
-> that's comes because we installed the API-Platfrom. So I want it to be an API resource I answer with "yes"

... and then error...

In DoctrineHelper.php line 314:

  Warning: Invalid argument supplied for foreach()

Okay, because I have no idea what the problem is I googeling and found that this can be happen because of an older version of the maker-bundle. (Post a GitHub Issue - Link)

I take a look on Packagist.org to find the lastest version which I can use.

I decide to update to version 1.35 of the maker-bundle because it works with my php version 7.1.3 and also it's the last version which require Symfony version 4.0 later versions using Symfony 4.4.

So in my composer.json I changed the version of the maker-bundle from "^1.12" to "^1.35.0".

Digression "^"-operator
If I understand the documentation for the versioning of bundles in the composer.json right - and I not sure I do - (Link)
the "^"-operator is to accept a version range of this bundle to the next versioning level which I have specified. I my case I think "^1.35.0" is the range of "1.35.0 to < 1.36"

Okay back on track I run:

composer update --with-all-dependencies

... it runs and ends successfully, but strange, composer told me:

...
Nothing to modify in lock file
Writing lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove

So it seems that composer did not make any changes. To get the information which version is installed I run

composer show

Which tells me that the maker-bundle is installed in version 1.35:

...
symfony/maker-bundle  v1.35.0   Symfony Maker
...

... so it seems to me that it was already installed in version 1.35. I take a look in the composer.lock file of a backup and yes it already was on version 1.35 before I updated it. In the future I should check the versions before make a change in the composer.json

So that's not solves my problem with creating an entity.

Next I try the default action and clear the composer cache with:

composer clearcache

... makes not different, still the same error by creating an entity...

Found the next article which refers to this error (GitHub).
... at the end I think need to update the maker-bundle to version 1.36.
But for me it seems that I also have to update my Symfony version to 4.4 as a requirement of the maker-bundle 1.36.

So because I don't see another way to solve my problem I'll update my Symfony version to 4.4.
Post: Updateing Symfony 4.2 to 4.4

After I has updated my Symfony version to 4.4, I see that also the maker-bundle was updated to version 1.39.0, so hopefully this has solved my problem too.

Let's figure out by running again:

php bin/console make:entity

This time after Q2: it dose not drops an error, yeah...

So let's go-ahead and creating some properties "name" and "age"

Q3:
New property name (press <return> to stop adding fields):
-> name

Field type (enter ? to see all types) [string]:
-> string

Field length [255]:
-> 255

Can this field be null in the database (nullable) (yes/no) [no]:
->

Add the other property "age"

Q4:
Add another property? Enter the property name (or press <return> to stop adding fields):
-> age

Field type (enter ? to see all types) [string]:
-> integer

Can this field be null in the database (nullable) (yes/no) [no]:
-> no

Then exit the dialog by clicking enter.

At the end I get the message

Success! 


Next: When you're ready, create a migration with php bin/console make:migration

So let's do that with the command:

php bin/console make:migration

If the user you used with doctrine to access your database did not have the right to create a table you will get the following error message:

In DBALException.php line 185:

  An exception occurred while executing 'CREATE TABLE migration_versions (version NVARCHAR(14) NOT NULL, executed_at DATETIME NOT NULL, PRIMARY KEY (version))':  

  SQLSTATE [42000, 262]: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]CREATE TABLE permission denied in database 'BCMS_FERON'.                           


In Error.php line 45:

  SQLSTATE [42000, 262]: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]CREATE TABLE permission denied in database '<dbName>'.

After I extend the permission for this user the command runs successfully, perfect.

And as before in the terminal we find the message what we should do next:

 Success! 


 Next: Review the new migration "src/Migrations/Version20220621131505.php"
 Then: Run the migration with php bin/console doctrine:migrations:migrate

Okay I go on an run the recommended command:

php bin/console doctrine:migrations:migrate

After confirm the question:

WARNING! You are about to execute a database migration that could result in schema changes and data loss. Are you sure you wish to continue? (y/n)

which I answering with "yes", it runs and fails.

Looks like doctrine has a problem with parts of the structure of the database. Because I didn't want to figure out what exactly the problem is, I decide to reduce the created migration-file (you can find it at src/Migrations/Version.php) in a way that only the entries for the new entity "apiTest" is still inside.

So in the end in the migration-file is nothing more then create-SQL statement for this new table:

CREATE TABLE api_test (id INT IDENTITY NOT NULL, name NVARCHAR(255) NOT NULL, age INT NOT NULL, PRIMARY KEY (id))

(you can easily go directly into the database and create the table with this statement by your self)

After that change, the command:
php bin/console doctrine:migrations:migrate
runs without an error.

And we done - creating an entity with the maker-bundle and migrate it to the database.

Updating Symfony 4.2 to 4.4

JerDox — Tue, 21 Jun 2022 12:56:39 +0000

I've worked a long time with Symfony 4.2 and I never had the need to update it in the last years.

But now I it seems to me that I have to update min. to version 4.4. because of an error in the maker-bundle which was seems to be fixed in a version that needs Symfony 4.4. (GitHub Issue)

So let's start:
In my existing Symfony Project my composer.json looking like this:

{
    "type": "project",
    "license": "proprietary",
    "require": {
        "php": "^7.1.3",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "api-platform/core": "2.1",
        "doctrine/annotations": "^1.0",
        "doctrine/doctrine-bundle": "^1.11",
        "doctrine/doctrine-migrations-bundle": "^2.0",
        "doctrine/orm": "^2.7",
        "nelmio/cors-bundle": "^1.5 || ^2.0",
        "phpdocumentor/reflection-docblock": "^3.0 || ^4.0 || ^5.0",
        "sensio/framework-extra-bundle": "^5.2",
        "symfony/apache-pack": "^1.0",
        "symfony/asset": "4.2.*",
        "symfony/console": "4.2.*",
        "symfony/dotenv": "4.2.*",
        "symfony/expression-language": "4.2.*",
        "symfony/flex": "^1.1",
        "symfony/framework-bundle": "4.2.*",
        "symfony/security-bundle": "4.2.*",
        "symfony/twig-bundle": "4.2.*",
        "symfony/validator": "4.2.*",
        "symfony/webpack-encore-bundle": "^1.7",
        "symfony/yaml": "4.2.*"
    },
    "config": {
        "preferred-install": {
            "*": "dist"
        },
        "sort-packages": true,
        "allow-plugins": {
            "ocramius/package-versions": true,
            "symfony/flex": true
        }
    },
    "autoload": {
        "psr-4": {
            "App\\": "src/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "App\\Tests\\": "tests/"
        }
    },
    "replace": {
        "paragonie/random_compat": "2.*",
        "symfony/polyfill-ctype": "*",
        "symfony/polyfill-iconv": "*",
        "symfony/polyfill-php71": "*",
        "symfony/polyfill-php70": "*",
        "symfony/polyfill-php56": "*"
    },
    "scripts": {
        "auto-scripts": {
            "cache:clear": "symfony-cmd",
            "assets:install %PUBLIC_DIR%": "symfony-cmd"
        },
        "post-install-cmd": [
            "@auto-scripts"
        ],
        "post-update-cmd": [
            "@auto-scripts"
        ]
    },
    "conflict": {
        "symfony/symfony": "*"
    },
    "extra": {
        "symfony": {
            "allow-contrib": false,
            "require": "4.2.*"
        }
    },
    "require-dev": {
        "symfony/debug-bundle": "4.2.*",
        "symfony/maker-bundle": "^1.35.0",
        "symfony/monolog-bundle": "^3.0",
        "symfony/stopwatch": "4.2.*",
        "symfony/web-profiler-bundle": "4.2.*"
    }
}

1. Step:
I changed all references of "symfony/..." with the version "4.2" inside to "4.4.*" ('*' is specify a wildcard. That means that the updates can be >= 4.4.0 and < 4.5 if I've understand that correctly) (composer docs)

2. Step:
I open a terminal and navigate to the directory where the Symfony-Project is lives in and run:

composer update symfony/* --with-all-dependencies

... and YES for my surprise it succeeded without any error message. This was much easier as I expected.

There is also a good tutorial for updating Symfony to version 4.4 on Symfonycast

Symfony (4.2) installing "API- Platfrom" for using Web-Services

JerDox — Tue, 21 Jun 2022 07:54:18 +0000

I have a Symfony (4.2) project and need to setup/communicate with a web-service.
So after a short search I found that there is a package for Symfony which should makes handling of web-services easy.
It's called "API Platform".

On Symfonycast I found a video of how to install the API-Platform Symfonycast

Sounds easy, so let's do it by easily run the command

composer require api:1.2.0

to install api-platfrom via composer

... and it fails with the message:

require.api is invalid, it should have a vendor name, a forward slash, and a package name. The vendor and package name can be words separated by -, . or _. The complete name should match "^[a-z0-9]([_.-]?[a-z0-9]+)*/[a-z0-9](([_.]?|-{0,2})[a-z0-9]+)*$".

For me it seems that it did not find the api recipe. So on the github page of the Symfony/flex Bundle I found the List of existing recipes RecipeList and in it there was no "api" recipe only a "api-platform/core" recipe. So I tryed that with:

composer require api-platform/core

... and it fails again this time with another error message:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - symfony/flex is locked to version v1.6.2 and an update of this package was not requested.
    - symfony/flex v1.6.2 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.3.0] but it does not match the constraint.
  Problem 2
    - api-platform/core[v2.6.0, ..., v2.6.6] require symfony/http-foundation ^4.4 || ^5.1 -> found symfony/http-foundation[v4.4.0, ..., v4.4.42, v5.1.0, ..., v5.4.9] but the package is fixed to v4.2.12 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - api-platform/core[v2.6.7, ..., v2.6.8] require symfony/http-foundation ^4.4 || ^5.1 || ^6.0 -> found symfony/http-foundation[v4.4.0, ..., v4.4.42, v5.1.0, ..., v5.4.9, v6.0.0, ..., v6.1.1] but the package is fixed to v4.2.12 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.  
    - Root composer.json requires api-platform/core ^2.6 -> satisfiable by api-platform/core[v2.6.0, ..., v2.6.8].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require api-platform/core:*" to figure out if any version is installable, or "composer require api-platform/core:^2.1" if you know which you need.

...as the message said in the last sentence, I try it with:

composer require api-platform/core:*

...also not working. Message:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - symfony/flex is locked to version v1.6.2 and an update of this package was not requested.
    - symfony/flex v1.6.2 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.3.0] but it does not match the constraint.

Next I try it with the option "--with-all-dependencies" which was also recommended in the error message before. So I run:

composer require api-platform/core:* --with-all-dependencies

... it ends up with the same error message as before.

I take a look back to the Symfonycast tutorial. On the page it the possibility to see the composer.json which was used in the tutorial. I see that the symfony version was the same as my "4.2" the api-platform/core was of version "^2.1". So I tried the command with the version "^2.1":

composer require api-platform/core:^2.1 --with-all-dependencies

... nope, not working, error message:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - symfony/flex is locked to version v1.6.2 and an update of this package was not requested.
    - symfony/flex v1.6.2 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.3.0] but it does not match the constraint.
  Problem 2
    - ocramius/package-versions 1.4.2 requires composer-plugin-api ^1.0.0 -> found composer-plugin-api[2.3.0] but it does not match the constraint.
    - doctrine/doctrine-migrations-bundle 2.1.2 requires doctrine/migrations ^2.2 -> satisfiable by doctrine/migrations[2.2.1].
    - symfony/orm-pack v1.0.8 requires doctrine/doctrine-migrations-bundle * -> satisfiable by doctrine/doctrine-migrations-bundle[2.1.2].
    - doctrine/migrations 2.2.1 requires ocramius/package-versions ^1.3 -> satisfiable by ocramius/package-versions[1.4.2].
    - symfony/orm-pack is locked to version v1.0.8 and an update of this package was not requested.

That's frustrating :/ ...

Next what I was going to do was to clear the cache of composer, in hope that that's the problem. I run

composer clearcache
That's done without any error message and then run again:

composer require api-platform/core:^2.1 --with-all-dependencies

... nope that don't make a different...

Okay, next thing I've done was to delete my composer.lock and my vendor-folder and do a complete install of the dependencies with:

composer install

Next error. This time after composer installed all dependencies and then try to clear the cache. Message:

Script cache:clear returned with error code 1
!!
!!  In ArrayNode.php line 331:
!!  

!!    Unrecognized options "dir_name, namespace" under "doctrine_migrations". Available options are "all_or_nothing", "check_database_platform", "connection
"
!!    , "custom_template", "em", "factories", "migrations", "migrations_paths", "organize_migrations", "services", "storage".

!!  

!!
!!
Script @auto-scripts was called via post-update-cmd

After a short googleing it seems that this error comes from the doctrine/doctrine-migrations-bundle dependency which should be use in version 2.0 but installed was 3.0.
So I changed the corresponding entry of this package in the composer.json to version 2.0 and run:

composer update --with-all-dependencies

...and surprise done without an error message.
Okay new hope for my actual problem.
As a reminder I want to install the api-platform with composer...

So I run again:

composer require api-platform/core:^2.1 --with-all-dependencies

... and YES it installed the api-platfrom dependency without an error messages. I hadn't believed in it anymore after this chain of error (pain).

Supplement:
As I continued with the Tutorial from Symfonycast I saw that with the origin command

composer require api:1.2.0

they installed not only just the api-platform/core bundle but also some other bundles with seems to be helpful.

They installes a package with called api-platform/api-pack which contains the following child bundles:

api-platform/core
nelmio/cors-bundle
symfony/asset
symfony/expression-language
symfony/orm-pack
symfony/security-bundle
symfony/serializer-pack
symfony/twig-bundle
symfony/validator

I think that I also need those bundles later on. So back in the "rabbit hole of dependencies" I run:

composer require api-platform/api-pack:1.2.2 --with-all-dependencies

...runs and ...also successful, puhhh yeah.

I used the version 1.2.2 of the api-pack, because this was the latest version in which the api-platfrom/core:2.1 was included.
Those Informations about the composer bundles you can find under:

Packagist

See you next time in the dependency hell...