Javascript setup is not compatible with npm 7 / 8 / 9 #88

niklasnatter · 2021-02-09T14:06:23Z

The javascript setup in the assets/admin folder uses the file:... syntax to require Sulu packages such as the sulu-admin-bundle:

skeleton/assets/admin/package.json

Lines 15 to 28 in c9640ee

    
           "sulu-admin-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/AdminBundle/Resources/js", 
        
           "sulu-audience-targeting-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/AudienceTargetingBundle/Resources/js", 
        
           "sulu-category-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/CategoryBundle/Resources/js", 
        
           "sulu-contact-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/ContactBundle/Resources/js", 
        
           "sulu-custom-url-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/CustomUrlBundle/Resources/js", 
        
           "sulu-location-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/LocationBundle/Resources/js", 
        
           "sulu-media-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/MediaBundle/Resources/js", 
        
           "sulu-page-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/PageBundle/Resources/js", 
        
           "sulu-preview-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/PreviewBundle/Resources/js", 
        
           "sulu-route-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/RouteBundle/Resources/js", 
        
           "sulu-search-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/SearchBundle/Resources/js", 
        
           "sulu-security-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/SecurityBundle/Resources/js", 
        
           "sulu-snippet-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/SnippetBundle/Resources/js", 
        
           "sulu-website-bundle": "file:../../vendor/sulu/sulu/src/Sulu/Bundle/WebsiteBundle/Resources/js"

Dependencies that are required like this will be symlinked into the assets/admin/node_moules directory. Unfortunately, npm v7 does not install the dependencies of these dependencies at the moment: npm/cli#2339

Because of this, the dependencies of the Sulu bundles are not installed and the build fails with a lot of error messages like this:

ERROR in /sulu-skeleton/vendor/sulu/sulu/src/Sulu/Bundle/AdminBundle/Resources/js/components/Tabs/Tabs.js
Module not found: Error: Can't resolve 'classnames' in '/sulu-skeleton/vendor/sulu/sulu/src/Sulu/Bundle/AdminBundle/Resources/js/components/Tabs'
 @ /sulu-skeleton/vendor/sulu/sulu/src/Sulu/Bundle/AdminBundle/Resources/js/components/Tabs/Tabs.js 54:0-36 347:22-32
 @ /sulu-skeleton/vendor/sulu/sulu/src/Sulu/Bundle/AdminBundle/Resources/js/components/Tabs/index.js
 @ /sulu-skeleton/vendor/sulu/sulu/src/Sulu/Bundle/AdminBundle/Resources/js/components/index.js
 @ /sulu-skeleton/vendor/sulu/sulu/src/Sulu/Bundle/ContactBundle/Resources/js/components/ContactDetails/Phone.js
 @ /sulu-skeleton/vendor/sulu/sulu/src/Sulu/Bundle/ContactBundle/Resources/js/index.js
 @ ./index.js

The text was updated successfully, but these errors were encountered:

niklasnatter · 2021-03-10T08:31:04Z

Fixed by sulu/sulu#5859 and #96 🎉
To understand why the fix works, the following comment that was added in sulu/sulu#5859 in the symlink-vendor-directory.js might be helpful:

// the sulu/skeleton uses the assets/admin directory as root directory for the administration interface javascript
// application. this application imports the sulu/sulu code by requiring the bundles from the the vendor directory
// in its package.json.
//
// unfortunately this setup causes various problems in the javascript ecosystem because the assets/admin directory
// is not an ancestor of the vendor/sulu/sulu directory which is used to require the code of bundles. for example,
// npm 7 does not install the dependencies of the bundle packages (https://github.com/npm/cli/issues/2339) and older
// npm versions are not able to dedupe packages that are required by a bundle and in the assets/admin directory.
// because of this, packages that were not deduped might be included in the webpack build multiple times. this
// increases the size of the build and will lead to an error in case of the @ckeditor packages:
// http://ckeditor.com/docs/ckeditor5/latest/framework/guides/support/error-codes.html#error-ckeditor-duplicated-modules
//
// to prevent these problems, this file creates a assets/admin/node_modules/node_modules/@sulu/vendor symlink and we
// use the symlinked vendor directory to require the bundles in the assets/admin/package.json.
// this makes the directory that is used for requiring the bundles a descendant of the assets/admin directory and
// allows npm to correctly dedupe the installed packages.

alexander-schranz · 2021-03-10T17:53:19Z

Damn seems like it doesn't actually work. Really not sure why but currently tested by me and @chirimoya and the packages of the subpackages where not installed. Not sure why or if there was maybe again a change in npm or node, but with current:

[ 0s064 | Mär 10 06:52pm ] [ 0 ]
~/D/S/s/a/admin (2.x|✚5…) $ npm --version
7.6.2

[ 0s881 | Mär 10 06:52pm ] [ 0 ]
~/D/S/s/a/admin (2.x|✚5…) $ node --version
v15.11.0

it didn't work for me 😢 😠 😡 . So it seems like I did only fix the ckeditor issue and windows build not the npm 😞

niklasnatter · 2021-03-11T09:00:38Z

Thanks for reopening - thats really sad to hear 😢
Maybe we need to add the symlink outside of the node_modules folder for npm7 compatibility? I could imagine that npm7 does not install the dependencies if a package is inside of the node_modules folder 🤔

alexander-schranz · 2021-03-11T09:08:04Z

Did test it yesterday but outside node_modules didn't work for me. Not sure why it did work sometime 🙈

niklasnatter · 2021-03-11T09:11:58Z

Okay thats a pity - I guess we need to hope that npm/cli#2339 gets resolved soon then 😕

madwizard-thomas · 2021-04-23T13:41:35Z

For me it does seem to work if the symlink is outside node_modules, but inside the admin dir.
So using ../../vendor/sulu/.. does not resolve dependencies, neither does the now default symlink in node_modules/@sulu/vendor/...

However if I symlink assets/admin/sulu to ../../vendor/sulu/sulu and use file:sulu/src/Sulu/Bundle'... as dependency paths it does work.

For npm 7 it would also work to just add the list of sulu module directories as an array to the workspaces section of package.json and remove them from the dependencies section (still requires a symlink in trhe admin dir though). This will also resolve the dependencies. It will also break on incompatible react version peer dependencies (npm 7 installs peer dependencies by default and will complain about conflicts). That may need to be resolved but with npm install --legacy-peer-deps it does work.

madwizard-thomas · 2021-04-26T08:17:56Z

One issue I'm still having with this setup is that if the node_modules directory in the root exists, the symlinked package will resolve modules from this directory. The build will succeed but the code won't actually work (wrong version of path-to-regexp causes errors for example). If it doesn't exists everything works fine.
I think this is caused by npm using the resolved path (realpath) of the symlinks to search the modules.

niklasnatter · 2021-04-26T09:38:05Z

Hey,
thanks a lot for spending your time on this. We really appreciate your help here!

For me it does seem to work if the symlink is outside node_modules, but inside the admin dir.
So using ../../vendor/sulu/.. does not resolve dependencies, neither does the now default symlink in node_modules/@sulu/vendor/...

However if I symlink assets/admin/sulu to ../../vendor/sulu/sulu and use file:sulu/src/Sulu/Bundle'... as dependency paths it does work.

We tried this initially, but we decided against a symlink outside of the node_modules folder because of DX. When we tested this, it broke the autocompletion/refactoring capabilities of our IDE because the IDE indexed the content of the assets/admin/sulu symlink as part of the source code. Placing the symlink in the node_modules solved this because the IDE treated the symlinked file as dependency code.

For npm 7 it would also work to just add the list of sulu module directories as an array to the workspaces section of package.json and remove them from the dependencies section (still requires a symlink in trhe admin dir though). This will also resolve the dependencies.

This is really good to know, thanks! Unfortunately this setup will not work with npm 6, right? I think I would prefer such a setup as soon as there is a Node.js LTS release that includes npm 7 per default.

One issue I'm still having with this setup is that if the node_modules directory in the root exists, the symlinked package will resolve modules from this directory. The build will succeed but the code won't actually work (wrong version of path-to-regexp causes errors for example). If it doesn't exists everything works fine.

Do you mean the root of the project? Who creates this node_modules folder in the root?
I think this problem exists with the current setup in the repository too. As far as I understand, the problem is related to how webpack resolves dependencies (relative to the file that is processed). Unfortunately, I think that this is a quirk with our setup/project structure and we cannot do anything here.

madwizard-thomas · 2021-04-26T11:12:12Z

We tried this initially, but we decided against a symlink outside of the node_modules folder because of DX.

I see!

Unfortunately this setup will not work with npm 6, right?

Yes

Do you mean the root of the project? Who creates this node_modules folder in the root?

Yes, this is the node_modules used for the website itself (webpack/encore).

As far as I understand, the problem is related to how webpack resolves dependencies (relative to the file that is processed). Unfortunately, I think that this is a quirk with our setup/project structure and we cannot do anything here.

It is the module resolution that node use, there doesn't seem to be much to influence that. I can't see any workarounds either other than building the admin separately (or with docker for example).

niklasnatter · 2021-04-26T11:18:27Z

Yes, this is the node_modules used for the website itself (webpack/encore).
It is the module resolution that node use, there doesn't seem to be much to influence that. I can't see any workarounds either other than building the admin separately (or with docker for example).

I think you are right 😕
We configure webpack/encore to use the assets/website folder instead of the project root in our projects. There is a small guide in the documentation how to do this (hopefully it is still up-to-date, havent used this in the last months): https://docs.sulu.io/en/2.2/cookbook/webpack-encore.html

alexander-schranz · 2021-10-07T21:48:16Z

Sadly custom build still don't work under npm 7/8. The related issue npm/cli#2339 still exists.

AndreasA · 2022-02-23T15:47:17Z

@alexander-schranz Will NPM actually fix this because I am not that sure. Maybe you should implement a separate solution instead after all the issue is over a year old and it makes development more tricky due to admin/website might require different NPM versions

alexander-schranz · 2022-02-23T16:07:16Z

@AndreasA there is already in discussion to use module federation or ddl builds so every bundle provides build version of the code itself and not a project need to compile also the code of the bundles.

See also sulu/sulu#6343 (comment)

To test that out we first need upgrade to webpack 5. Currently ckeditor was the blocking point there. They fixed that with the latest release 32.0.0 release.

At current state if you need to switch npm versions you maybe want to create .nvmrc in your project to achieve that the correct version is used.

alexander-schranz · 2022-04-28T08:00:18Z

There was an update on the linked issue: npm/cli#2339 (comment)

So it is now possible to install the dependencies with npm 8.8.0. Sadly there seems to be no way to support npm 6 and npm 8.8.

NPM 6 requires that we include our dependencies over a local child:

file:node_modules/@sulu/vendor/sulu/sulu/src/Sulu/Bundle/AdminBundle/Resources/js

NPM 8.8 seems not to like that and requires an include over:

file:../../vendor/sulu/sulu/src/Sulu/Bundle/AdminBundle/Resources/js

One change which effects our development process NPM 6 did install the dependencies as symlinks and make so development easier. NPM 8.8 will pack the dependency and install a copy of it, which will make for us the sulu development harder.

Still it seems the package installation work. Node 18 or 17 seems not be compatible with webpack 4, both errors in:

node:internal/crypto/hash:67 this[kHandle] = new _Hash(algorithm, xofLen);

> build
> webpack --mode production

node:internal/crypto/hash:67
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:67:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/webpack/lib/NormalModule.js:471:10)
    at /Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/webpack/lib/NormalModule.js:503:5
    at /Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/webpack/lib/NormalModule.js:358:12
    at /Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at iterateNormalLoaders (/Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
    at /Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/loader-runner/lib/LoaderRunner.js:236:3
    at context.callback (/Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at /Users/alexanderschranz/Documents/Projects/sulu-develop.localhost/assets/admin/node_modules/babel-loader/lib/index.js:59:71 {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.0.0

Node 16 (current LTS) with npm 8.8 seems to work.

Solutions for Node 17 / 18 problems seems to update to webpack 5 or use the workaround here: webpack/webpack#13572 (comment) which I tested and did work when adding that lines to sulu webpack config. The major change here is that it will change the hash algorithm and so generate a completely new files also for all static content (fonts, images, ...) which did not change.

alexander-schranz · 2022-11-29T22:06:01Z

I tried NPM 9 where the --install-links is now default.

Still it seems the package installation work. Node 18 or 17 seems not be compatible with webpack 4, both errors in:
node:internal/crypto/hash:67 this[kHandle] = new _Hash(algorithm, xofLen);

This issue still exist but, there seems currently workaround for this when doing:

export NODE_OPTIONS=--openssl-legacy-provider

Still npm 8.8 and 9 does not create symlinks which make developing sulu itself only possible inside the sulu/sulu package itself not outside of it. Like written above it is not possible to be compatible to npm 6, 7, 8 and 8.8, 9. So we would force that versions.

So best solution still would be update to webpack 5 and introducing the webpack 5 module federations. Which would also remove the whole dependencies symlink issues.

alexander-schranz · 2022-11-30T09:36:39Z

I forgot to add I also tried https://github.com/mweststrate/relative-deps package from mweststrate the creator of mobx. Sadly this does also not work as it seems require yarn, versions in package + that the package is published on npm registry. Which make it not usable for us to work with local dependencies.

simontol · 2023-03-28T07:39:21Z

Workaround:
npm i -D npm@6 # install npm@6.x as dev dependecy
npx npm install # npx runs npm from node_modules/.bin
npx npm run build

fnagel · 2023-09-06T15:40:42Z

Any news on this? NodeJS 16 support will end in September 2023.

I've tried this with v16.19.1 (which comes with npm v8.19.3 by default) and it does not work. Needed to downgrade npm.

alexander-schranz · 2023-09-06T16:10:56Z

No currently we have not any news here, downgrade or using docker for projects which overwrites something is still required: https://docs.sulu.io/en/2.5/cookbook/build-admin-frontend.html#solution-2-build-manually-with-docker

arjanfrans · 2023-10-18T09:22:45Z

Any timeline when this will be updated?

With Node 14 I still have to use the old install script from https://github.com/nodesource/distributions. Which now even prompts with an annoying timeout of 60 seconds to make me aware of having to upgrade.

alexander-schranz · 2023-10-18T09:47:03Z

Requirement is npm@6 on which node version you run NPM 6 is up to you. I personally use still 14 but our CI Node 16. There is not a timeline yet because the npm issue still not resolved.

alexander-schranz · 2023-11-21T23:58:13Z

I did test a little bit with bun as an alternative to npm, yarn, pnpm currently bun can be used with any node or npm version to build sulu as it is its own binary. What is required in that case is to run preinstall manually. The linked issue on bun is this one oven-sh/bun#4914.

But when run:

bun run preinstall
bun install

bun run build

If bun will adopt in future some of the npm dependencies behaviour I'm not sure but atleast currently from verison 1.0.0->1.0.13 it works like expected.

simontol · 2023-12-04T10:40:26Z

Bun 1.0.15
Sulu 2.5.10
I get the following error when trying to install deps with bun run preinstall:

$ node ../../vendor/sulu/sulu/preinstall.js
vendor/sulu/sulu/preinstall.js:4
    throw new Error('\x1b[31mYou must use "npm install", yarn is not supported\x1b[0m');
    ^

Error: You must use "npm install", yarn is not supported
    at Object.<anonymous> (/home/simone/Work/elite_local/EPW/vendor/sulu/sulu/preinstall.js:4:11)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
    at internal/main/run_main_module.js:17:47
error: script "preinstall" exited with code 1 (SIGHUP)

alexander-schranz · 2023-12-04T10:53:08Z

@simontol The build with bun is only part of sulu/sulu 2.6@dev yet.

spackmat · 2023-12-13T16:35:00Z

Hey, it is another problem, but closely related: Using Node > v16 leads to errors:

Error: error:0308010C:digital envelope routines::unsupported

The solution is to downgrade node to v16 or just set the --openssl-legacy-provider node option. That answer on StackOverflow describes that for Unix-like, Windows CMD and Powershell. I just wanted to leave that here if someone runs into that.

alexander-schranz · 2023-12-13T17:04:26Z

@spackmat Thx for the hint. I also had that openssl issue in the past in older PHP applications. So I patched locally my openssl config this way: https://stackoverflow.com/questions/73832854/php-openssl-pkcs12-read-error0308010cdigital-envelope-routinesunsupported/73858615#73858615. I think the problem should not appear when using docker like documented:

https://docs.sulu.io/en/2.5/cookbook/build-admin-frontend.html#solution-2-build-manually-with-docker

alexander-schranz · 2024-02-15T18:29:36Z

If somebody want to help move things forward here. Please give the changes of #235 a try.

alexander-schranz · 2024-03-15T09:56:34Z

With the merge of #235 and sulu/sulu#7286 we can finally close this issue. Support for newer versions of npm and support of pnpm and bun will be part of Sulu 2.6. Yarn (all versions yeah they really already have 4) are not supported because how they handle local dependencies. Here the current full list which are supported by the admin build:

npm
- ❌ <= 7
- ✅ 8, 9, 10
pnpm
- ⚠️ <= 7 not tested
- ✅ 8
bun
- ✅ 1
yarn
- ❌ 1, 2, 3, 4

This only effects the admin build, for the website / your own CSS build you are still free to use which version and package manager you want to use.

alexander-schranz added the bug Something isn't working label Feb 9, 2021

This was referenced Mar 4, 2021

Add pre and post install script for symlink sulu/sulu#5856

Closed

Add symlink to vendor directory in node_modules directory in preinstall and postinstall script sulu/sulu#5859

Merged

niklasnatter closed this as completed Mar 10, 2021

alexander-schranz reopened this Mar 10, 2021

niklasnatter mentioned this issue Mar 11, 2021

Remove misleading sentence about npm 7 compatibility from symlink-vendor-directory.js script sulu/sulu#5871

Merged

niklasnatter mentioned this issue Apr 1, 2021

Specify supported npm versions in package.json and enable engine-strict to check npm version on install #102

Merged

FlxSaenger referenced this issue May 11, 2021

Update package.json to install react 17 (#122)

cf73e34

alexander-schranz mentioned this issue Jun 16, 2021

Using npm workspaces for local dependencies #131

Closed

lubomirfiala mentioned this issue Aug 18, 2021

npm 7 fails while resolving dependencies before validating supported engines #133

Closed

alexander-schranz changed the title ~~Javascript setup is not compatible with npm 7~~ Javascript setup is not compatible with npm 7 / 8 Oct 7, 2021

alexander-schranz pinned this issue Nov 18, 2021

danrot mentioned this issue Dec 22, 2021

Outdated javascript dependencies sulu/sulu#6343

Open

1 task

alexander-schranz mentioned this issue Apr 28, 2022

Dropping Support for npm 6 in favor of npm 8.8 sulu/sulu#6566

Closed

alexander-schranz changed the title ~~Javascript setup is not compatible with npm 7 / 8~~ Javascript setup is not compatible with npm 7 / 8 / 9 Nov 29, 2022

This was referenced Nov 21, 2023

Add experimental support for bun sulu/sulu#7206

Merged

Add experimental support for bun #230

Merged

alexander-schranz mentioned this issue Nov 22, 2023

Add hint to use bun to build admin sulu/sulu-docs#782

Merged

alexander-schranz mentioned this issue Feb 15, 2024

Add support for NPM 8, 9, 10 and PNPM 8, remove support for NPM 6 #235

Merged

alexander-schranz mentioned this issue Feb 15, 2024

Add support for NPM 8, 9, 10 and PNPM 8, remove support for NPM 6 sulu/sulu#7286

Merged

alexander-schranz closed this as completed Mar 15, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Javascript setup is not compatible with npm 7 / 8 / 9 #88

Javascript setup is not compatible with npm 7 / 8 / 9 #88

niklasnatter commented Feb 9, 2021

niklasnatter commented Mar 10, 2021

alexander-schranz commented Mar 10, 2021

niklasnatter commented Mar 11, 2021 •

edited

Loading

alexander-schranz commented Mar 11, 2021

niklasnatter commented Mar 11, 2021 •

edited

Loading

madwizard-thomas commented Apr 23, 2021

madwizard-thomas commented Apr 26, 2021

niklasnatter commented Apr 26, 2021 •

edited

Loading

madwizard-thomas commented Apr 26, 2021 •

edited

Loading

niklasnatter commented Apr 26, 2021 •

edited

Loading

alexander-schranz commented Oct 7, 2021 •

edited

Loading

AndreasA commented Feb 23, 2022

alexander-schranz commented Feb 23, 2022

alexander-schranz commented Apr 28, 2022 •

edited

Loading

alexander-schranz commented Nov 29, 2022 •

edited

Loading

alexander-schranz commented Nov 30, 2022

simontol commented Mar 28, 2023

fnagel commented Sep 6, 2023

alexander-schranz commented Sep 6, 2023

arjanfrans commented Oct 18, 2023

alexander-schranz commented Oct 18, 2023

alexander-schranz commented Nov 21, 2023 •

edited

Loading

simontol commented Dec 4, 2023 •

edited

Loading

alexander-schranz commented Dec 4, 2023

spackmat commented Dec 13, 2023 •

edited

Loading

alexander-schranz commented Dec 13, 2023 •

edited

Loading

alexander-schranz commented Feb 15, 2024

alexander-schranz commented Mar 15, 2024 •

edited

Loading

Javascript setup is not compatible with npm 7 / 8 / 9 #88

Javascript setup is not compatible with npm 7 / 8 / 9 #88

Comments

niklasnatter commented Feb 9, 2021

niklasnatter commented Mar 10, 2021

alexander-schranz commented Mar 10, 2021

niklasnatter commented Mar 11, 2021 • edited Loading

alexander-schranz commented Mar 11, 2021

niklasnatter commented Mar 11, 2021 • edited Loading

madwizard-thomas commented Apr 23, 2021

madwizard-thomas commented Apr 26, 2021

niklasnatter commented Apr 26, 2021 • edited Loading

madwizard-thomas commented Apr 26, 2021 • edited Loading

niklasnatter commented Apr 26, 2021 • edited Loading

alexander-schranz commented Oct 7, 2021 • edited Loading

AndreasA commented Feb 23, 2022

alexander-schranz commented Feb 23, 2022

alexander-schranz commented Apr 28, 2022 • edited Loading

alexander-schranz commented Nov 29, 2022 • edited Loading

alexander-schranz commented Nov 30, 2022

simontol commented Mar 28, 2023

fnagel commented Sep 6, 2023

alexander-schranz commented Sep 6, 2023

arjanfrans commented Oct 18, 2023

alexander-schranz commented Oct 18, 2023

alexander-schranz commented Nov 21, 2023 • edited Loading

simontol commented Dec 4, 2023 • edited Loading

alexander-schranz commented Dec 4, 2023

spackmat commented Dec 13, 2023 • edited Loading

alexander-schranz commented Dec 13, 2023 • edited Loading

alexander-schranz commented Feb 15, 2024

alexander-schranz commented Mar 15, 2024 • edited Loading

niklasnatter commented Mar 11, 2021 •

edited

Loading

niklasnatter commented Mar 11, 2021 •

edited

Loading

niklasnatter commented Apr 26, 2021 •

edited

Loading

madwizard-thomas commented Apr 26, 2021 •

edited

Loading

niklasnatter commented Apr 26, 2021 •

edited

Loading

alexander-schranz commented Oct 7, 2021 •

edited

Loading

alexander-schranz commented Apr 28, 2022 •

edited

Loading

alexander-schranz commented Nov 29, 2022 •

edited

Loading

alexander-schranz commented Nov 21, 2023 •

edited

Loading

simontol commented Dec 4, 2023 •

edited

Loading

spackmat commented Dec 13, 2023 •

edited

Loading

alexander-schranz commented Dec 13, 2023 •

edited

Loading

alexander-schranz commented Mar 15, 2024 •

edited

Loading